From: Junio C Hamano <gitster@pobox.com>
To: "Martin Ågren" <martin.agren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Feb 2021, #03; Wed, 17)
Date: Thu, 18 Feb 2021 11:31:25 -0800 [thread overview]
Message-ID: <xmqqczwxfa0i.fsf@gitster.g> (raw)
In-Reply-To: <CAN0heSqHLzGSZ87GLo8dm854ZOMONCv0c69YFX_=40q5wG66JQ@mail.gmail.com> ("Martin Ågren"'s message of "Thu, 18 Feb 2021 07:44:29 +0100")
Martin Ågren <martin.agren@gmail.com> writes:
> On Thu, 18 Feb 2021 at 03:13, Junio C Hamano <gitster@pobox.com> wrote:
>> * ma/doc-markup-fix (2021-02-17) 2 commits
>> - gitmailmap.txt: fix rendering of e-mail addresses
>> - rev-list-options.txt: fix rendering of bonus paragraph
>>
>> Docfix.
>>
>> Will merge to 'next'.
>
> Thanks for picking it up.
Thanks for contributing.
> It looks like you didn't pick up the middle(!) one, "git.txt: fix
> monospace rendering". I thought maybe you queued it somewhere else, but
> I can't seem to find it anywhere. Chris, and later Patrick, had a
> question about it, which was maybe why you skipped it. I hope I've
> resolved that confusion, which was entirely caused by my cramming
> something too diff-like into the commentary of the patch.
Yeah, I too commented on that one myself just now. It is a mystery
how I managed to miss the entire discussion (including the starting
patch in the middle of a 3-patch series) yesterday.
> Obviously, that patch 2/3 doesn't need to go in the middle -- it can
> just as well be at the top.
>
> Martin
next prev parent reply other threads:[~2021-02-18 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 2:11 What's cooking in git.git (Feb 2021, #03; Wed, 17) Junio C Hamano
2021-02-18 3:19 ` Matheus Tavares Bernardino
2021-02-18 18:25 ` Junio C Hamano
2021-02-18 6:44 ` Martin Ågren
2021-02-18 19:31 ` Junio C Hamano [this message]
2021-02-18 10:44 ` Charvi Mendiratta
2021-02-18 19:36 ` Junio C Hamano
2021-02-19 6:14 ` Charvi Mendiratta
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=xmqqczwxfa0i.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=martin.agren@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.