From: Andreas Schwab <schwab@linux-m68k.org>
To: git-scm@webhippo.net
Cc: <git@vger.kernel.org>
Subject: Re: Bug Report: Creating a hardlink to any of the file in git repo cause the source file to show up in git commit message editor under "Changes not staged for commit" section.
Date: Mon, 18 Jul 2011 22:12:18 +0200 [thread overview]
Message-ID: <m28vrvfivx.fsf@igel.home> (raw)
In-Reply-To: <6f37875d70623e2b8966653b067a2149@mail.mxes.net> (Michael's message of "Sun, 17 Jul 2011 20:24:50 -0700")
Michael <git-scm@webhippo.net> writes:
> In case anyone interested, tor me this happens when I do a python EGG
> build
> which hardlinks files in order to build.
Try "git config core.trustctime false". Adding a link changes ctime.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2011-07-18 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 3:24 Bug Report: Creating a hardlink to any of the file in git repo cause the source file to show up in git commit message editor under "Changes not staged for commit" section Michael
2011-07-18 20:12 ` Andreas Schwab [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-18 3:42 Michael
2011-07-18 18:37 ` Junio C Hamano
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=m28vrvfivx.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git-scm@webhippo.net \
--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).