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

Re: [PATCH 2/2] merge-base: "--reflog" mode finds fork point from reflog entries

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 24, 2013, 21:26 UTC
Message-ID
<xmqq61smmkc0.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CAPig+cQrBMMqSmOk0GSZJ9PTHNt-t+vuOG2Aq=7VTR1EZSeLsw@mail.gmail.com>
Eric Sunshine <sunshine@sunshineco.com> writes:
Show 25 quoted lines
> On Thu, Oct 24, 2013 at 3:11 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> diff --git a/t/t6010-merge-base.sh b/t/t6010-merge-base.sh
>> index f80bba8..3a1abee 100755
>> --- a/t/t6010-merge-base.sh
>> +++ b/t/t6010-merge-base.sh
>> @@ -230,4 +230,31 @@ test_expect_success 'criss-cross merge-base for octopus-step' '
>>         test_cmp expected.sorted actual.sorted
>>  '
>>
>> +test_expect_success 'using reflog to find the fork point' '
>> +       git reset --hard &&
>> +       git checkout -b base $E &&
>> +       (
>> +               for count in 1 2 3 4 5
>> +               do
>> +                       git commit --allow-empty -m "Base commit #$count" &&
>> +                       git rev-parse HEAD >expect$count &&
>> +                       git checkout -B derived &&
>> +                       git commit --allow-empty -m "Derived #$count" &&
>> +                       git rev-parse HEAD >derived$count &&
>> +                       git checkout base &&
>> +                       count=$(( $count + 1 )) || exit 1
>> +               done
>
> Did you want && here?

No, I did not. Can't you tell from the fact that I didn't put one there ;-)?

It does not hurt to have one there, but it is not necessary.

Because the loop itself does not &&-cascade from anything else, the only case anything after "done &&" would be skipped and making the whole thing fail would be when anything inside the loop fails, but we already "exit 1" to terminate the whole subprocess in that case, so we will not continue past the loop.

Show 8 quoted lines
>> +
>> +               for count in 1 2 3 4 5
>> +               do
>> +                       git merge-base --reflog base $(cat derived$count) >actual &&
>> +                       test_cmp expect$count actual || exit 1
>> +               done
>
> And here?
Likewise.
Thanks.
Show 8 quoted lines
>> +
>> +               # check defaulting to HEAD
>> +               git merge-base --reflog base >actual &&
>> +               test_cmp expect5 actual
>> +       )
>> +'
>> +
>>  test_done
Previous: Eric SunshineNext: Eric Sunshine
Message 12 of 35 in “rebase: use reflog to find common base with upstream”
  1. rebase: use reflog to find common base with upstreamJohn Keeping, Oct 16, 2013
  2. Jonathan NiederOct 16, 2013
  3. John KeepingOct 16, 2013
  4. Martin von ZweigbergkOct 21, 2013
  5. John KeepingOct 21, 2013
  6. Martin von ZweigbergkOct 22, 2013
  7. Junio C HamanoOct 24, 2013
  8. 0/2 finding the fork point from reflog entriesJunio C Hamano, Oct 24, 2013
  9. 1/2 merge-base: use OPT_CMDMODE and clarify the command line parsingJunio C Hamano, Oct 24, 2013
  10. 2/2 merge-base: "--reflog" mode finds fork point from reflog entriesJunio C Hamano, Oct 24, 2013
  11. Eric SunshineOct 24, 2013
  12. Junio C HamanoOct 24, 2013
  13. Eric SunshineOct 24, 2013
  14. Junio C HamanoOct 24, 2013
  15. 2/2 merge-base: "--reflog" mode finds fork point from reflog entriesJunio C Hamano, Oct 24, 2013
  16. Johannes SixtOct 25, 2013
  17. John KeepingOct 25, 2013
  18. Johannes SixtOct 25, 2013
  19. Junio C HamanoOct 25, 2013
  20. 2/2 merge-base: teach "--fork-point" modeJunio C Hamano, Oct 25, 2013
  21. Eric SunshineOct 25, 2013
  22. Martin von ZweigbergkOct 26, 2013
  23. Junio C HamanoOct 28, 2013
  24. John KeepingOct 26, 2013
  25. Junio C HamanoOct 28, 2013
  26. John KeepingOct 29, 2013
  27. Junio C HamanoOct 29, 2013
  28. John KeepingOct 24, 2013
  29. Junio C HamanoOct 24, 2013
  30. John KeepingOct 24, 2013
  31. John KeepingOct 24, 2013
  32. John KeepingOct 24, 2013
  33. Junio C HamanoOct 25, 2013
  34. Martin von ZweigbergkOct 22, 2013
  35. John KeepingOct 24, 2013

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.