From: newren@gmail.com
To: git@vger.kernel.org
Cc: Johannes.Schindelin@gmx.de, Elijah Newren <newren@gmail.com>
Subject: [PATCH] Add new testcase to show that fast-export can squash merge commits
Date: Tue, 10 Feb 2009 23:03:52 -0700 [thread overview]
Message-ID: <1234332233-10017-1-git-send-email-newren@gmail.com> (raw)
From: Elijah Newren <newren@gmail.com>
Signed-off-by: Elijah Newren <newren@gmail.com>
---
I'm not certain this testcase will actually trigger the bug for everyone,
since I don't know the order of commits used by git rev-list. It does
trigger it for me. What you need is a history that looks like
B--D
/ /
A--C
with the master branch pointing at D, and have "git rev-list --all" show
these commits in the order
C
D
B
A
If you have such a repository, "git fast-export --all" will give
instructions to create a master branch that only contains D, B, and A.
t/t9301-fast-export.sh | 29 +++++++++++++++++++++++++++++
1 files changed, 29 insertions(+), 0 deletions(-)
diff --git a/t/t9301-fast-export.sh b/t/t9301-fast-export.sh
index 9985721..a1ee400 100755
--- a/t/t9301-fast-export.sh
+++ b/t/t9301-fast-export.sh
@@ -259,4 +259,33 @@ test_expect_success 'cope with tagger-less tags' '
'
+test_expect_success 'avoid squashing merges' '
+
+ mkdir repo &&
+ cd repo &&
+ git init &&
+ echo fee-fi-fo-fum > giant &&
+ git add giant &&
+ git commit -m "Initial commit" &&
+ git branch alternate_root &&
+ echo hello > world &&
+ git add world &&
+ git commit -m "Commit on master" &&
+ git checkout alternate_root &&
+ echo foo > bar &&
+ git add bar &&
+ git commit -m "Commit on alternate_root" &&
+ git checkout master &&
+ git merge alternate_root &&
+ MASTER=$(git rev-parse --verify refs/heads/master) &&
+ rm -rf ../new &&
+ mkdir ../new &&
+ git --git-dir=../new/.git init &&
+ git fast-export --all |
+ (cd ../new &&
+ git fast-import &&
+ test $MASTER = $(git rev-parse --verify refs/heads/master))
+
+'
+
test_done
--
1.6.0.6
next reply other threads:[~2009-02-11 6:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 6:03 newren [this message]
2009-02-11 6:03 ` [PATCH] fast-export: ensure we traverse commits in topological order newren
2009-02-11 10:25 ` Johannes Schindelin
2009-02-11 10:48 ` Mike Ralphson
2009-02-11 10:59 ` Johannes Schindelin
2009-02-11 13:56 ` Jeff King
2009-02-11 15:18 ` Johannes Schindelin
2009-02-11 17:37 ` Jeff King
2009-02-11 15:23 ` Elijah Newren
2009-02-11 17:53 ` Jeff King
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=1234332233-10017-1-git-send-email-newren@gmail.com \
--to=newren@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).