git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCHv3 1/2] t5520-pull: Add testcases showing spurious conflicts from git pull --rebase

From
Elijah Newren <newren@gmail.com>
Date
Aug 9, 2010, 19:22 UTC
Message-ID
<AANLkTin0xvK8H8RvaXtmaNHJh1dStn0AN1Mqed7JGvuO@mail.gmail.com>
In-Reply-To
<7vfwyn61td.fsf@alter.siamese.dyndns.org>
On Mon, Aug 9, 2010 at 1:09 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Elijah Newren <newren@gmail.com> writes:
<snip>
Show 11 quoted lines
>> +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"
>        }

I copied this function verbatim from t/t4127-apply-same-fn.sh. Would you like me to fix that one too?

Show 8 quoted lines
>> +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.

Yes, Hannes pointed out the same issue. Does the follow-up interdiff I posted in response to my patch address this in a way you'd like?

Previous: Junio C HamanoNext: Ævar Arnfjörð Bjarmason
Message 5 of 7 in “[PATCHv3 0/2] Fix spurious conflicts with pull --rebase”
  1. Elijah NewrenAug 8, 2010
  2. 1/2 t5520-pull: Add testcases showing spurious conflicts from git pull --rebaseElijah Newren, Aug 8, 2010
  3. Elijah NewrenAug 9, 2010
  4. Junio C HamanoAug 9, 2010
  5. Elijah NewrenAug 9, 2010
  6. Ævar Arnfjörð BjarmasonAug 9, 2010
  7. 2/2 pull --rebase: Avoid spurious conflicts and reapplying unnecessary patchesElijah Newren, Aug 8, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.