From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: git@vger.kernel.org, santi@agolina.net,
Johannes.Schindelin@gmx.de, avarab@gmail.com
Subject: Re: [PATCHv3 1/2] t5520-pull: Add testcases showing spurious conflicts from git pull --rebase
Date: Mon, 09 Aug 2010 12:09:02 -0700 [thread overview]
Message-ID: <7vfwyn61td.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1281300917-5610-2-git-send-email-newren@gmail.com> (Elijah Newren's message of "Sun\, 8 Aug 2010 14\:55\:16 -0600")
Elijah Newren <newren@gmail.com> writes:
> Signed-off-by: Elijah Newren <newren@gmail.com>
> ---
> t/t5520-pull.sh | 63 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 63 insertions(+), 0 deletions(-)
>
> diff --git a/t/t5520-pull.sh b/t/t5520-pull.sh
> index 319e389..9099e55 100755
> --- a/t/t5520-pull.sh
> +++ b/t/t5520-pull.sh
> @@ -4,6 +4,11 @@ test_description='pulling into void'
>
> . ./test-lib.sh
>
> +modify () {
> + sed -e "$1" < "$2" > "$2".x &&
> + mv "$2".x "$2"
> +}
Just a style thing but I'd prefer to see the above written like this:
modify () {
sed -e "$1" <"$2" >"$2.x" &&
mv "$2.x" "$2"
}
> +test_expect_success 'setup for avoiding reapplying old patches' '
> + (cd dst &&
> + git rebase --abort;
This may be hypothetical but this discards error condition from failing to
ch into dst (for whatever reason). Don't we expect "git rebase --abort"
to exit with a non-zero status? Same comment for the last one in the
patch below.
> +test_expect_failure 'git pull --rebase does not reapply old patches' '
> + (cd dst &&
> + git pull --rebase;
> + test 1 = $(find .git/rebase-apply -name "000*" | wc -l)
> + )
> +'
> +
> test_done
Thanks.
next prev parent reply other threads:[~2010-08-09 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-08 20:55 [PATCHv3 0/2] Fix spurious conflicts with pull --rebase Elijah Newren
2010-08-08 20:55 ` [PATCHv3 1/2] t5520-pull: Add testcases showing spurious conflicts from git " Elijah Newren
2010-08-09 0:43 ` Elijah Newren
2010-08-09 19:09 ` Junio C Hamano [this message]
2010-08-09 19:22 ` Elijah Newren
2010-08-09 20:35 ` Ævar Arnfjörð Bjarmason
2010-08-08 20:55 ` [PATCHv3 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=7vfwyn61td.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--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).