Re: [PATCH v3 00/20] fundamentals of merge-ort implementation

From: Elijah Newren <newren@gmail.com>
Date: Dec 14, 2020, 16:24 UTC
Message-ID: <CABPp-BFkXcxMR=2kh6mBR5ymy2s5-Gdngw182SUs5EweZdj-fw@mail.gmail.com>
In-Reply-To: <5fd77584dda74_d1ec120827@natae.notmuch>

On Mon, Dec 14, 2020 at 6:24 AM Felipe Contreras <felipe.contreras@gmail.com> wrote:

Show 15 quoted lines

>
> Elijah Newren via GitGitGadget wrote:
> > This is actually v5 of this series, and is being sent due to review comments
> > from a different series, namely en/merge-ort-3[1].
> >
> > I have rerolls of en/merge-ort-2 and en/merge-ort-3 already prepared, but
> > since gitgitgadget will not allow me to send a series dependent on a
> > not-published-by-Junio series, I cannot yet send them. You will need to
> > temporarily drop them, and I'll resend after you publish the updated version
> > of this series. I do not like this solution, and I was tempted to just push
> > the updates into en/merge-ort-3, but since this series was still hanging in
> > 'seen' awaiting feedback and a lot of the suggestions were for things from
> > this series, I decided to go this route anyway...
>
> You could send it the old-fashioned way.

As mentioned in the first line of the message, I already did the first two rounds that way. There are sometimes reasons to use send-email, but gitgitgadget comes with really nice cross-platform testing so I do tend to prefer it. Also, mix-and-matching between send-email and gitgitgadget causes some confusion on which-number-in-the-series-is-it counts (as noted above), so I tend to avoid it.