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

Re: the meaning of keephardlinks

From
Geoff Russell <geoffrey.russell@gmail.com>
Date
Jan 13, 2009, 03:30 UTC
Message-ID
<93c3eada0901121930n16dd2e83v452c38fd30da5054@mail.gmail.com>
In-Reply-To
<alpine.DEB.1.00.0901130141190.3586@pacific.mpi-cbg.de>
On 1/13/09, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
Show 23 quoted lines
> Hi,
>
>
>  On Tue, 13 Jan 2009, Geoff Russell wrote:
>
>  > I'm curious about what keephardlinks means.
>  >
>  > If I do: "ln X Y ; git add Y ; git commit" in my origin and then
>  > "git pull" in my cloned repository,
>  > should I get a hard linked file in the clone
>  > when core.keephardlinks is set to true?
>
>
> Nope.
>
>  It means that if you have a hard link locally, it will stay a hard link
>  (and if it is modified, the other linked files will obviously change,
>  too).
>
>  Note that this feature is not even in 'next'.
>
>  Ciao,
>  Dscho
Fine. Thanks,
Geoff.
Previous: Johannes Schindelin
Message 3 of 3 in “the meaning of keephardlinks”
  1. Geoff RussellJan 13, 2009
  2. Johannes SchindelinJan 13, 2009
  3. Geoff RussellJan 13, 2009

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.