From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Mon, 13 Oct 2008 17:54:02 GMT
Subject: Re: [PATCH] Introduce core.keepHardLinks
Message-ID: <alpine.DEB.1.00.0810131950140.22125@pacific.mpi-cbg.de.mpi-cbg.de>
In-Reply-To: <7vhc7g9z7s.fsf@gitster.siamese.dyndns.org>

Hi,

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

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > - all the editors that this guy tested keep the hard links, so it was 
> >   kinda hard to understand why Git insists on behaving differently,
> >
> > - if the user asked for hard links, it is not Git's place to question 
> >   that decision,
> 
> These are non-arguments,

Actually, they are arguments.

The thing is: these editors do what they do for a reason.  Which is 
exactly the second reason.

When a user makes hard links, it is not just for fun and bullocks.  It is 
not for copy-on-write either, that's not what hard links are supposed to 
do.  It is for cases when you need the _same_ information in two places.

I am not that big a user of hard links myself, but when I do, I know 
exactly what I am doing.  And with my patch and that config variable set 
to true, Git will not interfer with that.

Ciao,
Dscho