git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elijah Newren <newren@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@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 14:17:45 -0600	[thread overview]
Message-ID: <AANLkTimsfcSB7GMcNnZSBiwH4kwZeEazo5svW96_Nf9J@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikhsFfCfmR2V8iSRvU73B5yW=_kqJAEfAGgxpLY@mail.gmail.com>

Hi,

Thanks for taking a look!

On Sun, Aug 8, 2010 at 2:01 PM, Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> On Sun, Aug 8, 2010 at 19:04, Elijah Newren <newren@gmail.com> wrote:
<snip>
>> +        perl -pi -e s/5/43/ stuff &&
>> +        git commit -a -m "5->43" &&
>> +        perl -pi -e s/6/42/ stuff &&
>
> Please use sed so the test doesn't depend on perl being present.

The original series used 'sed -i', but I found out that is apparently
not portable.  Should I use sed + a temporary file + mv?

<snip>
>> +test_expect_success 'setup for avoiding reapplying old patches' '
>> +       (cd dst &&
>> +        (git rebase --abort || true) &&
>
> If you're ignoring the git rebase --abort return value:
>
>  (cd dst &&
>    git rebase --abort;
>    git reset ...)

Makes sense; I'll do that.

  reply	other threads:[~2010-08-08 20:17 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 [this message]
2010-08-08 20:33       ` Ævar Arnfjörð Bjarmason
2010-08-08 21:36   ` Johannes Sixt
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=AANLkTimsfcSB7GMcNnZSBiwH4kwZeEazo5svW96_Nf9J@mail.gmail.com \
    --to=newren@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).