From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kay Sievers <kay.sievers@vrfy.org>, git@vger.kernel.org
Subject: Re: git and symlinks as tracked content
Date: Tue, 03 May 2005 12:50:33 -0700 [thread overview]
Message-ID: <4277D609.5050701@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0505031151240.26698@ppc970.osdl.org>
Linus Torvalds wrote:
>
> So you have
>
> - directories: S_IFDIR (0040000) point to "tree" objects for contents
> - symlinks: S_IFLNK (0120000) point to "blob" objects
> - executables: S_IFREG | 0755 (0100755) point to "blob" objects
> - regular files: S_IFREG | 0644 (0100644) point to "blob" objects
>
> which seems very sane and regular.
>
One thing about using a hierarchy of "tree" objects... as far as I
understand today, it's possible for "git" to represent a limited
scattering of files underneath the root, such as keeping one's
configuration files underneath one's home directory. Scanning the whole
home directory to check in (or worse, out) files would suck.
On the other hand, having a single "tree" object for a large project
that would have to be constantly updated would suck, too.
This is certainly *not* mutually exclusive; it's mostly a matter of
making sure that if scaffolding directory objects are necessary, that
they can be automatically added/created, and aren't exhaustively
searched for uncontrolled objects.
> Now, I also haev a plan for device nodes, but that one is so ugly that I'm
> a bit ashamed of it. That one does:
>
> - S_IFCHR/S_IFBLK (0020000 or 0060000), with the 20-byte SHA1 not being a
> SHA1 at all, but just the major:minor numbers in some nice binary
> encoding. Probably: two network byte order 32-bit values, with twelve
> bytes of some non-zero signature (the SHA1 of all zeroes should be
> avoided, so the signature really should be soemthing else than just
> twelve bytes of zero).
>
OK, that's ugly. I'm impressed. :)
-hpa
next prev parent reply other threads:[~2005-05-03 19:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 18:33 git and symlinks as tracked content Kay Sievers
2005-05-03 19:02 ` Linus Torvalds
2005-05-03 19:10 ` Morten Welinder
2005-05-03 19:50 ` H. Peter Anvin [this message]
2005-05-03 19:57 ` Andreas Gal
2005-05-03 20:05 ` Linus Torvalds
2005-05-03 20:09 ` Kay Sievers
2005-05-03 21:30 ` Junio C Hamano
2005-05-03 21:51 ` Andreas Gal
2005-05-03 22:44 ` Junio C Hamano
2005-05-04 0:39 ` Sym-links, b/c-special files, pipes, ... Scope Creep Brian O'Mahoney
2005-05-03 22:56 ` git and symlinks as tracked content H. Peter Anvin
2005-05-03 23:16 ` Junio C Hamano
2005-05-03 23:18 ` H. Peter Anvin
2005-05-03 23:42 ` Linus Torvalds
2005-05-03 23:42 ` Junio C Hamano
2005-05-04 15:48 ` David A. Wheeler
2005-05-04 23:03 ` Daniel Barkalow
2005-05-05 6:09 ` Alan Chandler
2005-05-05 9:51 ` read-only git repositories David Lang
2005-05-05 12:39 ` Sean
2005-05-06 3:01 ` read-only git repositories (ancient history) David A. Wheeler
2005-05-05 21:23 ` git and symlinks as tracked content Daniel Barkalow
2005-05-03 20:23 ` Junio C Hamano
2005-05-04 22:35 ` Kay Sievers
2005-05-04 23:16 ` Junio C Hamano
2005-05-05 1:20 ` Kay Sievers
2005-05-05 2:13 ` Junio C Hamano
2005-05-05 12:38 ` Kay Sievers
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4277D609.5050701@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=kay.sievers@vrfy.org \
--cc=torvalds@osdl.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).