From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Taylor Blau <me@ttaylorr.com>, Derrick Stolee <stolee@gmail.com>
Subject: Re: What's cooking in git.git (Jan 2021, #04; Sat, 16)
Date: Sat, 23 Jan 2021 23:03:49 -0800 [thread overview]
Message-ID: <xmqq35yq24ve.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CABPp-BHMmi1A2fzkVsgEUeeMQywtU6YaCU93nq1K7301YhtpjQ@mail.gmail.com> (Elijah Newren's message of "Sat, 23 Jan 2021 21:27:50 -0800")
Elijah Newren <newren@gmail.com> writes:
> On Thu, Jan 21, 2021 at 10:35 AM Junio C Hamano <gitster@pobox.com> wrote:
>> ...
>> Even though I wanted to merge the en/ort-directory-rename down to
>> 'next' yesterday, it has just got updated and I had to rebase the
>> ort-perf branch using the material from the old thread, so neither
>> is in 'next' as of now.
> ...
> reports, it's kinda important to get it right. So...
>
> * I'm not touching en/ort-directory-rename; I still think it is ready
> for merging to next.
By "not touching", do you mean you now want me to discard the latest
round that is on en/ort-directory-rename and revert the topic to the
previous version?
next prev parent reply other threads:[~2021-01-24 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 21:59 What's cooking in git.git (Jan 2021, #04; Sat, 16) Junio C Hamano
2021-01-21 16:25 ` Elijah Newren
2021-01-21 18:35 ` Junio C Hamano
2021-01-24 5:27 ` Elijah Newren
2021-01-24 7:03 ` Junio C Hamano [this message]
2021-01-24 7:10 ` Elijah Newren
2021-01-21 18:34 ` Jonathan Tan
2021-01-21 21:05 ` Jeff King
2021-01-21 23:10 ` Junio C Hamano
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=xmqq35yq24ve.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=newren@gmail.com \
--cc=stolee@gmail.com \
/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).