From: Junio C Hamano <gitster@pobox.com>
To: Philip Oakley <philipoakley@iee.email>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"René Scharfe" <l.s.r@web.de>, "Git List" <git@vger.kernel.org>
Subject: Re: [PATCH] mergesort: avoid left shift overflow
Date: Fri, 19 Nov 2021 11:28:38 -0800 [thread overview]
Message-ID: <xmqqlf1kosgp.fsf@gitster.g> (raw)
In-Reply-To: <05e6c0ab-7364-56d8-f0b2-e93c11b327e3@iee.email> (Philip Oakley's message of "Fri, 19 Nov 2021 17:27:23 +0000")
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.
next prev parent reply other threads:[~2021-11-19 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 23:19 [PATCH] mergesort: avoid left shift overflow René Scharfe
2021-11-16 14:08 ` Johannes Schindelin
2021-11-17 9:19 ` Junio C Hamano
2021-11-17 23:31 ` Johannes Schindelin
2021-11-18 23:27 ` Philip Oakley
2021-11-19 16:51 ` Johannes Schindelin
2021-11-19 17:15 ` René Scharfe
2021-11-19 17:27 ` Philip Oakley
2021-11-19 19:28 ` Junio C Hamano [this message]
2021-11-19 21:16 ` Philip Oakley
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=xmqqlf1kosgp.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--cc=philipoakley@iee.email \
/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).