From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: GIT_OBJECT_DIRECTORY
Date: Tue, 18 Apr 2006 20:58:59 +0200 [thread overview]
Message-ID: <20060418185859.GA7504@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0604181139150.3701@g5.osdl.org>
On Tue, 18 April 2006 11:47:53 -0700, Linus Torvalds wrote:
> On Tue, 18 Apr 2006, Jörn Engel wrote:
> >
> > But it appears as if I could "cp -lr" the git tree and work with that.
>
> That should work. I just personally fear cowlinks, because some things
> will edit the files in place, and then you're screwed.
s/cowlinks/hardlinks/ ?
The reason for me to write the cowlink patches was exactly the fear
you are talking about. With those patches, links are broken whenever
such a thing happens.
> I _think_ it should be ok for the .git subdirectory, but quite frankly,
> I'm not going to guarantee it. Also, you will break the cow-linking when
> you ever re-pack either the source or the destination, so you'd actually
In that case, cowlinks should still turn a blatant bug into some
wasted space - which is a hell of a lot better.
> # cow-link the checked-out state
And this happens to be a problem. Creating the links when the copy is
created is simple. Detecting identical files and linking them after
the fact is racy, complicated, racy and, well, racy. I wouldn't want
to touch it with a ten foot pole. Not without kernel support.
Jörn
--
Linux is more the core point of a concept that surrounds "open source"
which, in turn, is based on a false concept. This concept is that
people actually want to look at source code.
-- Rob Enderle
next prev parent reply other threads:[~2006-04-18 18:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 13:38 GIT_OBJECT_DIRECTORY Jörn Engel
2006-04-18 15:25 ` GIT_OBJECT_DIRECTORY Linus Torvalds
2006-04-18 17:58 ` GIT_OBJECT_DIRECTORY Jörn Engel
2006-04-18 18:07 ` GIT_OBJECT_DIRECTORY Sam Ravnborg
2006-04-18 18:08 ` GIT_OBJECT_DIRECTORY Linus Torvalds
2006-04-18 18:26 ` GIT_OBJECT_DIRECTORY Jörn Engel
2006-04-18 18:47 ` GIT_OBJECT_DIRECTORY Linus Torvalds
2006-04-18 18:58 ` Jörn Engel [this message]
2006-04-19 4:51 ` GIT_OBJECT_DIRECTORY H. Peter Anvin
2006-04-19 5:00 ` GIT_OBJECT_DIRECTORY Junio C Hamano
2006-04-18 18:20 ` GIT_OBJECT_DIRECTORY Junio C Hamano
2006-04-18 18:45 ` GIT_OBJECT_DIRECTORY Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2006-04-18 14:10 GIT_OBJECT_DIRECTORY linux
2006-04-18 14:16 ` GIT_OBJECT_DIRECTORY Jörn Engel
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=20060418185859.GA7504@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox