git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Josh England" <jjengla@sandia.gov>
To: "Jeff King" <peff@peff.net>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	git@vger.kernel.org
Subject: Re: tracking perms/ownership [was: empty directories]
Date: Fri, 24 Aug 2007 09:50:32 -0600	[thread overview]
Message-ID: <1187970632.6357.108.camel@beauty> (raw)
In-Reply-To: <20070824095217.GB16853@coredump.intra.peff.net>

On Fri, 2007-08-24 at 05:52 -0400, Jeff King wrote:
> On Fri, Aug 24, 2007 at 11:38:13AM +0200, Johannes Schindelin wrote:
> 
> > > So here's the initial thought.  Create two new gitattributes, 'perms'
> > > and 'ownership', which will track perms/ownership for files matching the
> > > given pattern.
> > 
> > I wonder why you do not just use the "smudge" and "clean" attributes, and 
> > store the ownership _and_ the permissions in .gitacls.
> > 
> > Yes, _maybe_ it is something other people might want, too, but let's start 
> > quick & easy, no?
> 
> Yes, I think that is a much better idea. Perhaps they aren't that
> popular among this crowd, but it seems silly to develop in this
> direction and not at least consider people storing actual ACLs (or even
> other extended attributes). An already-standard format like that
> produced by 'getfacl' should make this pretty trivial (and handles
> regular unix permissions at the same time).

Do you mean using acls through contrib/hooks/update-paranoid?  That is
the only place I see any mention of them.  clean and smudge seem out
because they are passed blob objects and have no notion of pathname.  I
don't see how to use this for automatic storing/restoring of
perms/ownership.

-JE

  reply	other threads:[~2007-08-24 15:49 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21 17:14 empty directories Josh England
2007-08-21 17:40 ` Sean
2007-08-22 21:25   ` Josh England
2007-08-22 23:25     ` Linus Torvalds
2007-08-22 23:55       ` David Kastrup
2007-08-23 15:24       ` Josh England
2007-08-23 21:51       ` tracking perms/ownership [was: empty directories] Josh England
2007-08-23 22:08         ` tracking perms/ownership Junio C Hamano
2007-08-23 23:30           ` Linus Torvalds
2007-08-24  6:16             ` David Kastrup
2007-08-24  6:37               ` Linus Torvalds
2007-08-24  7:38                 ` Josh England
2007-08-24  7:50                 ` David Kastrup
2007-08-24 17:51                   ` Linus Torvalds
2007-08-24 18:15                     ` Josh England
2007-08-24 18:23                       ` Linus Torvalds
2007-08-24 18:56                         ` Josh England
2007-08-24 20:37                           ` Junio C Hamano
2007-08-24 21:26                             ` Josh England
2007-08-24 19:33                       ` Robin Rosenberg
2007-08-24 21:30                     ` David Kastrup
2007-08-24  7:22           ` Josh England
2007-08-24  7:39             ` Junio C Hamano
2007-08-24  8:19               ` Josh England
2007-08-24 16:11           ` Josh England
2007-08-24 16:27             ` Josh England
2007-08-24  9:38         ` tracking perms/ownership [was: empty directories] Johannes Schindelin
2007-08-24  9:52           ` Jeff King
2007-08-24 15:50             ` Josh England [this message]
2007-08-24 20:58               ` Jeff King
2007-08-25 14:31                 ` Johannes Schindelin
2007-08-25 14:46                   ` tracking perms/ownership Junio C Hamano
2007-08-25 19:35                     ` Junio C Hamano
2007-08-24 10:05           ` tracking perms/ownership [was: empty directories] Jeff King
2007-08-25 14:30             ` Johannes Schindelin
2007-08-24 17:10       ` empty directories Jason Garber
2007-08-22 23:40     ` Jakub Narebski
2007-08-22  0:06 ` Jakub Narebski
2007-08-22  4:31 ` Salikh Zakirov
2007-08-22 18:46   ` Linus Torvalds
2007-08-22 19:12     ` David Kastrup

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=1187970632.6357.108.camel@beauty \
    --to=jjengla@sandia.gov \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=torvalds@linux-foundation.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).