threads / discuss / 17131

the meaning of keephardlinks

Subject: the meaning of keephardlinks

## tl;dr

3 messages between Jan 13, 2009 and Jan 13, 2009.

replies: 2people: 2as markdown or json

Geoff Russell· Jan 13, 2009, 00:17 UTC · lore
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?

Cheers, Geoff Russell

Johannes Schindelin· Jan 13, 2009, 00:42 UTC · re: Geoff Russell · lore

Re: the meaning of keephardlinks

Hi,
On Tue, 13 Jan 2009, Geoff Russell wrote:
Show 6 quoted lines
> 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

Geoff Russell· Jan 13, 2009, 03:30 UTC · re: Johannes Schindelin · lore

Re: the meaning of keephardlinks

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.

← back to recent threads