From: Johannes Sixt <j6t@kdbg.org>
To: Elijah Newren <newren@gmail.com>
Cc: gitster@pobox.com, git@vger.kernel.org, santi@agolina.net,
Johannes.Schindelin@gmx.de
Subject: Re: [PATCHv2 1/2] t5520-pull: Add testcases showing spurious conflicts from git pull --rebase
Date: Sun, 8 Aug 2010 23:36:18 +0200 [thread overview]
Message-ID: <201008082336.18270.j6t@kdbg.org> (raw)
In-Reply-To: <1281294286-27709-2-git-send-email-newren@gmail.com>
On Sonntag, 8. August 2010, Elijah Newren wrote:
> +test_expect_success 'setup for detecting upstreamed changes' '
> + mkdir src &&
> + (cd src &&
> + git init &&
> + for i in $(seq 1 10); do echo $i; done > stuff &&
We don't have seq on Windows. The sequence is short enough to list it
explicitly.
> + git add stuff &&
> + git commit -m "Initial revision"
> + ) &&
> + git clone src dst &&
> + (cd src &&
> + perl -pi -e s/5/43/ stuff &&
perl -pi is no better than sed -i; it does not work on Windows because it
tries to remove an open file (and that is a no-go on Windows). perl -pi.bak
does work though.
> + git commit -a -m "5->43" &&
> + perl -pi -e s/6/42/ stuff &&
> + git commit -a -m "Make it bigger" &&
> + correct=$(git rev-parse HEAD)
> + ) &&
This assignment at the end of the subshell is pointless.
> +test_expect_success 'setup for avoiding reapplying old patches' '
> + (cd dst &&
> + (git rebase --abort || true) &&
Perhaps:
test_might_fail git rebase --abort &&
but I'm not sure whether that's the intended use of test_might_fail.
> + git reset --hard origin/master
> + ) &&
...
> +test_expect_failure 'git pull --rebase does not reapply old patches' '
> + (cd dst &&
> + (git pull --rebase || true) &&
Ditto.
> + test 1 = $(find .git/rebase-apply -name "000*" | wc -l)
> + )
> +'
> +
> test_done
-- Hannes
next prev parent reply other threads:[~2010-08-08 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-08 19:04 [PATCHv2 0/2] Fix spurious conflicts with pull --rebase Elijah Newren
2010-08-08 19:04 ` [PATCHv2 1/2] t5520-pull: Add testcases showing spurious conflicts from git " Elijah Newren
2010-08-08 20:01 ` Ævar Arnfjörð Bjarmason
2010-08-08 20:17 ` Elijah Newren
2010-08-08 20:33 ` Ævar Arnfjörð Bjarmason
2010-08-08 21:36 ` Johannes Sixt [this message]
2010-08-08 21:43 ` Jonathan Nieder
2010-08-08 19:04 ` [PATCHv2 2/2] pull --rebase: Avoid spurious conflicts and reapplying unnecessary patches Elijah Newren
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=201008082336.18270.j6t@kdbg.org \
--to=j6t@kdbg.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=santi@agolina.net \
/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).