git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Introduce core.keepHardLinks

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Oct 13, 2008, 17:54 UTC
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:
Show 9 quoted lines
> 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

Previous: Junio C HamanoNext: Junio C Hamano
Message 10 of 14 in “Introduce core.keepHardLinks”
  1. Introduce core.keepHardLinksJohannes Schindelin, Oct 11, 2008
  2. Shawn O. PearceOct 12, 2008
  3. Johannes SchindelinOct 13, 2008
  4. Junio C HamanoOct 13, 2008
  5. Johannes SchindelinOct 13, 2008
  6. Stephan BeyerOct 13, 2008
  7. Shawn O. PearceOct 13, 2008
  8. Johannes SchindelinOct 13, 2008
  9. Junio C HamanoOct 13, 2008
  10. Johannes SchindelinOct 13, 2008
  11. Junio C HamanoOct 13, 2008
  12. Johannes SchindelinOct 15, 2008
  13. Junio C HamanoOct 13, 2008
  14. Johannes SchindelinOct 13, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.