From: Junio C Hamano <gitster@pobox•com>
To: Renich Bon Ciric <renich@woralelandia•com>
Cc: git@vger•kernel.org
Subject: Re: Feature: support for file permissions
Date: Thu, 24 Oct 2013 15:40:06 -0700 [thread overview]
Message-ID: <xmqqmwlyl2d5.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAGxGTk5eOGoUjrweZ9gLwBE6ev7oCZcu-aWWK2ydtpLkWgx8ew@mail.gmail.com> (Renich Bon Ciric's message of "Thu, 24 Oct 2013 16:32:36 -0500")
Renich Bon Ciric <renich@woralelandia•com> writes:
> I think file permissions are really important for source code as well.
>
> For example, in web development, you want configuration files to be
> read only; specially if you're deploying with git.
That is not _source code_; you are talking about deployed set of
files, and as you said, Git is about source code and is not a tool
for deployment.
> Please, consider supporting them.
See the ancient discussion around this:
http://thread.gmane.org/gmane.comp.version-control.git/375/focus=435
A short answer is that it is not likely to happen.
prev parent reply other threads:[~2013-10-24 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 21:32 Feature: support for file permissions Renich Bon Ciric
2013-10-24 22:40 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqmwlyl2d5.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=renich@woralelandia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox