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

Re: [PATCH] mergesort: avoid left shift overflow

From
Philip Oakley <philipoakley@iee.email>
Date
Nov 19, 2021, 21:16 UTC
Message-ID
<d9cdb708-1cd1-03e1-ea17-4195faafda76@iee.email>
In-Reply-To
<xmqqlf1kosgp.fsf@gitster.g>
On 19/11/2021 19:28, Junio C Hamano wrote:
Show 22 quoted lines
> Philip Oakley <philipoakley@iee.email> writes:
>
>>>> My patches are in https://github.com/PhilipOakley/git/tree/oneU_t
>>> How about rebasing the remaining patches from
>>> https://github.com/git-for-windows/git/compare/main...PhilipOakley:oneU_t
>>> on top of `rs/mergesort` and then submitting them, to avoid duplicate
>>> efforts?
>>>
>> I'm not finding a `rs/mergesort` at the moment. Any particular remote I
>> should find it on, or maybe a different spelling?
>> P.
> At https://github.com/gitster/git/, I publish the "broken out"
> branches.
>
> But resurrecting the tips of the topics should be fairly easy.
>
> $ git log --first-parent --oneline origin/master..origin/seen |
>   grep rs/mergesort
>
> The second parent of that merge is the tip of rs/mergesort topic
> back when the 'seen' integration branch was created.
>

Thanks. I'd been browsing via `gitk` and hadn't included all the tips, so couldn't find it at that point. I've got it now:  42c456ff81 (mergesort: avoid left shift overflow, 2021-11-16).

Philip
Previous: Junio C Hamano
Message 10 of 10 in “mergesort: avoid left shift overflow”
  1. mergesort: avoid left shift overflowRené Scharfe, Nov 15, 2021
  2. Johannes SchindelinNov 16, 2021
  3. Junio C HamanoNov 17, 2021
  4. Johannes SchindelinNov 17, 2021
  5. Philip OakleyNov 18, 2021
  6. Johannes SchindelinNov 19, 2021
  7. René ScharfeNov 19, 2021
  8. Philip OakleyNov 19, 2021
  9. Junio C HamanoNov 19, 2021
  10. Philip OakleyNov 19, 2021

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.