{"thread":{"id":"17131","subject":"the meaning of keephardlinks","startedAt":"2009-01-13T00:17:53Z","lastAt":"2009-01-13T03:30:07Z","messageCount":3,"participants":["Geoff Russell","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"100202","messageId":"93c3eada0901121617m43af82a7te946b1607fbf3f77@mail.gmail.com","threadId":"17131","inReplyTo":null,"subject":"the meaning of keephardlinks","fromName":"Geoff Russell","fromEmail":"geoffrey.russell@gmail.com","sentAt":"2009-01-13T00:17:53Z","receivedAt":"2009-01-13T00:17:53Z","isPatch":false,"sender":{"key":"geoffrey.russell@gmail.com","avatar":"https://gravatar.com/avatar/c30f497ccfa6bf06d86f30bd2ba092a2dd124c61c6bc902f7cb5c3f6486947de?d=mp&s=160"},"body":"I'm curious about what keephardlinks means.\n\nIf I do: \"ln X Y ; git add Y ; git commit\" in my origin and then\n\"git pull\" in my cloned repository,\nshould I get a hard linked file in the clone\nwhen core.keephardlinks is set to true?\n\nCheers,\nGeoff Russell\n"},{"id":"100205","messageId":"alpine.DEB.1.00.0901130141190.3586@pacific.mpi-cbg.de","threadId":"17131","inReplyTo":"93c3eada0901121617m43af82a7te946b1607fbf3f77@mail.gmail.com","subject":"Re: the meaning of keephardlinks","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2009-01-13T00:42:32Z","receivedAt":"2009-01-13T00:42:32Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Tue, 13 Jan 2009, Geoff Russell wrote:\n\n> I'm curious about what keephardlinks means.\n> \n> If I do: \"ln X Y ; git add Y ; git commit\" in my origin and then\n> \"git pull\" in my cloned repository,\n> should I get a hard linked file in the clone\n> when core.keephardlinks is set to true?\n\nNope.\n\nIt means that if you have a hard link locally, it will stay a hard link \n(and if it is modified, the other linked files will obviously change, \ntoo).\n\nNote that this feature is not even in 'next'.\n\nCiao,\nDscho\n"},{"id":"100228","messageId":"93c3eada0901121930n16dd2e83v452c38fd30da5054@mail.gmail.com","threadId":"17131","inReplyTo":"alpine.DEB.1.00.0901130141190.3586@pacific.mpi-cbg.de","subject":"Re: the meaning of keephardlinks","fromName":"Geoff Russell","fromEmail":"geoffrey.russell@gmail.com","sentAt":"2009-01-13T03:30:07Z","receivedAt":"2009-01-13T03:30:07Z","isPatch":false,"sender":{"key":"geoffrey.russell@gmail.com","avatar":"https://gravatar.com/avatar/c30f497ccfa6bf06d86f30bd2ba092a2dd124c61c6bc902f7cb5c3f6486947de?d=mp&s=160"},"body":"On 1/13/09, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:\n> Hi,\n>\n>\n>  On Tue, 13 Jan 2009, Geoff Russell wrote:\n>\n>  > I'm curious about what keephardlinks means.\n>  >\n>  > If I do: \"ln X Y ; git add Y ; git commit\" in my origin and then\n>  > \"git pull\" in my cloned repository,\n>  > should I get a hard linked file in the clone\n>  > when core.keephardlinks is set to true?\n>\n>\n> Nope.\n>\n>  It means that if you have a hard link locally, it will stay a hard link\n>  (and if it is modified, the other linked files will obviously change,\n>  too).\n>\n>  Note that this feature is not even in 'next'.\n>\n>  Ciao,\n>  Dscho\n\n\nFine. Thanks,\n\nGeoff.\n"}]}