All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danny van Delft <davd@bart.nl>
To: git@vger.kernel.org
Subject: Re: spurious fail of git merge after rebasing
Date: Mon, 18 Apr 2011 09:37:33 +0200	[thread overview]
Message-ID: <201104180937.33461.davd@bart.nl> (raw)
In-Reply-To: <201104160045.12633.davd@bart.nl>

[-- Attachment #1: Type: Text/Plain, Size: 1180 bytes --]

Added attachment contains testcases, in three separate dirs.

I came about this problem during development of a script that 
generates git commands to rebase a graph, with all its wanted 
sub graphs, starting at one commit onto another commit. The 
"runtest" script is the output of this script, hence the 
strange looking branchnames during its operation.

regards,
-- 
Danny
Op zaterdag 16 april 2011 om 00:45 schreef D. A. van Delft:
> Hi,
> 
> not sure if this is the right place, but I couldn't find a
> bugzilla or something for git.
> 
> Point is, I have found a scenario where sometimes git fails
> on a specific merge.
> Each time I start with the same identical git repository
> (archived once and restored each time before a run) and run
> the same fixed series of rebases and merges on it. Once in
> a while it fails with a merge conflict, sometimes at first
> try, sometimes after 10+ times. I have a canned set of
> testcases which reproduces this behaviour. I have also
> narrowed it down somewhat on how to work around, or
> prevent it from occurring.
> 
> However, given that it doesn't always fail or succeed, is
> unexpected.
> 
> regards,
> Danny A. van Delft

[-- Attachment #2: TestCases.tgz --]
[-- Type: application/x-compressed-tar, Size: 33304 bytes --]

      parent reply	other threads:[~2011-04-18  7:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15 22:45 spurious fail of git merge after rebasing D. A. van Delft
2011-04-18  6:10 ` Jeff King
2011-04-18  7:37 ` Danny van Delft [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=201104180937.33461.davd@bart.nl \
    --to=davd@bart.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.