Re: [PATCH] Introduce core.keepHardLinks

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Oct 15, 2008, 09:07 UTC
Message-ID: <alpine.DEB.1.00.0810151104400.22125@pacific.mpi-cbg.de.mpi-cbg.de>
In-Reply-To: <7v63nw9xor.fsf@gitster.siamese.dyndns.org>

Hi,

On Mon, 13 Oct 2008, Junio C Hamano wrote:

Show 7 quoted lines

> You could have said something like "The users may want to have a 
> checkout, and keep the same contents always appear elsewhere i.e. 
> 'installing by hardlinking'.  In such a setup, editing the source with 
> an editor configured not to break hardlinks would still work fine, but 
> git-checkout will unconditionally break such links, which is 
> undesirable.  Such a setup would want a configuration variable like 
> this."

Sounds very nice. Sorry for being grumpy, and not being able to come up with such a beautiful description.

> The documentation update needs to warn about the Shawn's scenario.  I also
> do not know what this should do when you have two tracked paths with
> identical contents hardlinked to each other.

When the user does that, it's the user's wish. I'd not let Git play cute games with that.

> It also raises another question.  Don't you want this to be an attribute 
> for paths, not all-or-nothing configuration per repository?

I'd rather not have it as an attribute, because it is not so much about file types that should show this behavior. It is more like an option that I fully expect to be set in $HOME/.gitconfig.

Ciao, Dscho