From: Alexander Gladysh <agladysh@gmail.com>
To: git@vger.kernel.org
Subject: False positives in git diff-index
Date: Mon, 27 Dec 2010 11:49:40 +0300 [thread overview]
Message-ID: <AANLkTimLW+J_rmRsqUQJO-9Gzn7aK0ZHkd1-s=Wg4Vbi@mail.gmail.com> (raw)
Hi, list!
I wrote about the related issue earlier:
http://lists-archives.org/git/731516-false-positives-from-git-diff-index-when-used-with-git-dir.html
Now I've got a case when I can reproduce this problem each time I try to.
Unfortunately I can not share it or create a minimal example — the
case is triggered by a custom complicated automated build process on a
private repository.
Anyway, I'm ready to debug this issue if someone will guide me.
Workflow:
<...change files in /path/dir1/...>
(cd /path && git add </path/dir1/>)
(cd /path && git commit -m <message1>)
... repeat change-add-commit several times for various directories
(can be the same directory or not) ...
<...generate file /path/dirN/foo...>
# Accidentally the file is generated the same as it was
(cd /path && git add </path/dirN/>)
(cd /path && git status) # Refresh index
(cd /path && git diff-index --exit-code --quiet HEAD -- /path/dirN) #
Incorrectly reports that there are some changes
(cd /path && git commit -m <messageN>) # fails, saying that there is
nothing to commit
If I insert sleep 10 between git status and git diff-index, the
problem goes away.
Any help?
Alexander.
next reply other threads:[~2010-12-27 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 8:49 Alexander Gladysh [this message]
2011-01-04 9:45 ` False positives in git diff-index Alexander Gladysh
2011-01-04 11:47 ` Zenaan Harkness
2011-01-04 12:01 ` Alexander Gladysh
2011-01-04 14:08 ` Jakub Narebski
2011-01-04 14:46 ` Alexander Gladysh
2011-01-05 5:48 ` Jeff King
2011-01-05 6:07 ` Alexander Gladysh
2011-01-05 6:15 ` Jeff King
2011-01-05 7:46 ` Alexander Gladysh
2011-01-05 8:08 ` Jeff King
2011-01-06 12:12 ` Alexander Gladysh
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='AANLkTimLW+J_rmRsqUQJO-9Gzn7aK0ZHkd1-s=Wg4Vbi@mail.gmail.com' \
--to=agladysh@gmail.com \
--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).