From: "Geoff Russell" <geoffrey.russell@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: the meaning of keephardlinks
Date: Tue, 13 Jan 2009 14:00:07 +1030 [thread overview]
Message-ID: <93c3eada0901121930n16dd2e83v452c38fd30da5054@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0901130141190.3586@pacific.mpi-cbg.de>
On 1/13/09, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> 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.
prev parent reply other threads:[~2009-01-13 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 0:17 the meaning of keephardlinks Geoff Russell
2009-01-13 0:42 ` Johannes Schindelin
2009-01-13 3:30 ` Geoff Russell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=93c3eada0901121930n16dd2e83v452c38fd30da5054@mail.gmail.com \
--to=geoffrey.russell@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).