git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Josh England <jjengla@sandia.gov>, git@vger.kernel.org
Subject: Re: tracking perms/ownership
Date: Thu, 23 Aug 2007 16:30:21 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.999.0708231626580.30176@woody.linux-foundation.org> (raw)
In-Reply-To: <7vtzqpsy3q.fsf@gitster.siamese.dyndns.org>



On Thu, 23 Aug 2007, Junio C Hamano wrote:
>
> "Josh England" <jjengla@sandia.gov> writes: 
> > Looking at the index struct, it already has fields in it for file mode
> > uid and gid (woohoo!).
> 
> I can see that storing textual names in gitattributes and having
> the root user run git so that it can chown(), would work.

Well, the nice thing is that even non-root can actually resolve merge 
conflicts and generally use the archive, even if non-root obviously cannot 
then actually set the files to those users/groups!

So handling ownership outside of the actual filesystem, in a separate file 
that git tracks, actually allows you to do things that you couldn't 
otherwise sanely do.

It obviously does have downsides:

> But this is only about checkout.  After you chown a file in the
> work tree and run update-index, next write-tree would not record
> it, as there is no place in tree objects to record uid/gid.

This is a direct consequence of allowing non-root to actually work with 
such a repository: the git-tracked ownership information simply is 
separate, and "git update-index" and friends will never do anything about 
it, since they just can't rely on the *filesystem* user/group information 
anyway (because normal users would never be allowed to set it, anyway).

		Linus

  reply	other threads:[~2007-08-23 23:31 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 [this message]
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
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=alpine.LFD.0.999.0708231626580.30176@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jjengla@sandia.gov \
    /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).