From: Chris Wedgwood <cw@f00f.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Matthias Urlichs <smurf@smurf.noris.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC PATCH] cogito --- don't overwrite metadata files in place (breaks CoW use)
Date: Wed, 13 Jul 2005 14:11:06 -0700 [thread overview]
Message-ID: <20050713211106.GA12047@taniwha.stupidest.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0507131402210.17536@g5.osdl.org>
On Wed, Jul 13, 2005 at 02:05:35PM -0700, Linus Torvalds wrote:
> > and .git/refs/head/master is hardlinked between both trees.
>
> AND THAT IS WRONG.
OK, I was more-or-less assuming that 'cp -Rl tree1 tree2' was always a
valid thing to do.
Clearly if it's not then all of this is somewhat moot.
> You shouldn't hardlink whole trees. Git will not guarantee that it
> breaks the links.
I can live with that, until now though I wasn't aware that hardlinked
trees were a bad-thing.
> Your script was tens of lines of code, and it was BUGGY.
Yeah well, I'm a retard.
> Hardlink git _object_ directories. That's a totally different thing.
I was under the misconception that hardlink entire trees was
permissible.
I would however like to be able to hardlink more than just the
_object_ directory --- hardlinking the source is quite nice too.
Might that be considered safe? (I'm of course assuming that editors
do write + rename when saving their buffers).
next prev parent reply other threads:[~2005-07-13 21:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 19:05 [RFC PATCH] cogito --- don't overwrite metadata files in place (breaks CoW use) Chris Wedgwood
2005-07-12 21:37 ` Junio C Hamano
2005-07-13 4:53 ` Chris Wedgwood
2005-07-13 7:03 ` Matthias Urlichs
2005-07-13 18:53 ` Chris Wedgwood
2005-07-13 20:05 ` Linus Torvalds
2005-07-13 20:44 ` Chris Wedgwood
2005-07-13 21:05 ` Linus Torvalds
2005-07-13 21:11 ` Chris Wedgwood [this message]
2005-07-13 21:33 ` Linus Torvalds
2005-07-13 21:50 ` Chris Wedgwood
2005-07-13 20:07 ` Matthias Urlichs
2005-07-13 20:36 ` Chris Wedgwood
2005-07-13 21:23 ` Linus Torvalds
2005-07-13 21:54 ` Chris Wedgwood
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=20050713211106.GA12047@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=git@vger.kernel.org \
--cc=smurf@smurf.noris.de \
--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