From: Kay Sievers <kay.sievers@vrfy.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andreas Gal <gal@uci.edu>, git@vger.kernel.org
Subject: Re: git and symlinks as tracked content
Date: Tue, 03 May 2005 22:09:19 +0200 [thread overview]
Message-ID: <1115150959.21105.116.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0505031304140.26698@ppc970.osdl.org>
On Tue, 2005-05-03 at 13:05 -0700, Linus Torvalds wrote:
>
> On Tue, 3 May 2005, Andreas Gal wrote:
> >
> > Yuck. Thats really ugly. Right now all files have a uniform touch to them.
> > For every hash you can locate the file, determine its type/tag, unpack it,
> > and check the SHA1 hash. The proposal above breaks all that. Why not just
> > introduce a new object type "dev" and put major minor in there. It
> > will still always hash to the same SHA1 hash value, but fits much better in the
> > overall design.
>
> Hey, I don't personally care that much. I don't see anybody using
> character device nodes in the kernel tree, and I don't think most SCM's
> support stuff like that anyway ;)
Well, you need to be root to create device nodes, that is not a usual
requirement for an SCM checkout. :)
Kay
next prev parent reply other threads:[~2005-05-03 20:03 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
2005-05-03 19:57 ` Andreas Gal
2005-05-03 20:05 ` Linus Torvalds
2005-05-03 20:09 ` Kay Sievers [this message]
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=1115150959.21105.116.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--cc=gal@uci.edu \
--cc=git@vger.kernel.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).