From: Jeff King <peff@peff.net>
To: John Goerzen <jgoerzen@complete.org>
Cc: git@vger.kernel.org
Subject: Re: git-rebase dirty index and email address bug?
Date: Tue, 4 Mar 2008 07:08:04 -0500 [thread overview]
Message-ID: <20080304120804.GA9042@sigill.intra.peff.net> (raw)
In-Reply-To: <200803022128.14511.jgoerzen@complete.org>
On Sun, Mar 02, 2008 at 09:28:14PM -0600, John Goerzen wrote:
> That repo contains some local configuration and password information.
> However, I would be happy to make it available to you or any other Git
> developer privately. Could you contact me off-list if you'd like me to send
> it to you? The .git directory in question is about 4.5MB, and I'd be happy
> to email it.
I was able to turn this into a much smaller test case.
What is happening is that rebase works something like:
1. reset to "onto" commit
2. replay each commit between "upstream" and "branch"
but there is a bug in step 1 that is leaving the bogus
"public/dispatch.fcgi" file in the index and working tree. So step 2
correctly complains that the file is already there and uncommitted.
The bug in step 1 seems to be very hard to trigger, and requires that
the "branch" commit and the "onto" commit differ such that:
- there is a file on the branch that was a directory in "onto"
- there is a file on the branch that is new since "onto", and that
sorts lexically after the file mentioned above
So you can see that it is rare for it to come up. :)
I'm not sure of the correct fix for the bug, but I have posted a request
for help under the subject "bug in unpack_trees", so hopefully somebody
more wise than I will have something to say.
-Peff
next prev parent reply other threads:[~2008-03-04 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 20:40 git-rebase dirty index and email address bug? John Goerzen
2008-03-01 21:29 ` John Goerzen
2008-03-02 7:30 ` Jeff King
2008-03-02 13:44 ` John Goerzen
2008-03-02 7:26 ` Jeff King
2008-03-03 3:28 ` John Goerzen
2008-03-04 12:08 ` Jeff King [this message]
2008-03-04 15:22 ` John Goerzen
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=20080304120804.GA9042@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=jgoerzen@complete.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).