git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Renich Bon Ciric <renich@woralelandia.com>
To: git@vger.kernel.org
Subject: Feature: support for file permissions
Date: Thu, 24 Oct 2013 16:32:36 -0500	[thread overview]
Message-ID: <CAGxGTk5eOGoUjrweZ9gLwBE6ev7oCZcu-aWWK2ydtpLkWgx8ew@mail.gmail.com> (raw)

Hello,

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.

Also, you would want some executable file to not be writable ; but
executable by world.

Permission support would become really handy when using GIT_WORK_TREE
on a bare repo.

Please, consider supporting them.

-- 
It's hard to be free... but I love to struggle. Love isn't asked for;
it's just given. Respect isn't asked for; it's earned!
Renich Bon Ciric

http://www.woralelandia.com/
http://www.introbella.com/

             reply	other threads:[~2013-10-24 21:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24 21:32 Renich Bon Ciric [this message]
2013-10-24 22:40 ` Feature: support for file permissions Junio C Hamano

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=CAGxGTk5eOGoUjrweZ9gLwBE6ev7oCZcu-aWWK2ydtpLkWgx8ew@mail.gmail.com \
    --to=renich@woralelandia.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).