From: Taylor Blau <firstname.lastname@example.org>
To: Philip Oakley <email@example.com>
Subject: Re: What's cooking in git.git (Nov 2022, #02; Tue, 8)
Date: Sun, 13 Nov 2022 00:08:21 -0500 [thread overview]
Message-ID: <Y3B7xf6UgO4aAQyy@nand.local> (raw)
On Sun, Nov 13, 2022 at 12:05:33AM -0500, Taylor Blau wrote:
> > I spotted some left-over comments at the test locations that needed QZ
> > space conversion in the here-docs, which have now been removed and a v4
> > submitted.
> Right. In this case only the WC report is out-of-date, since I picked up
> v4 in po/pretty-hard-trunc and pushed that out. That matches what's in
> 'seen', too.
Scratch that -- I mistakenly thought you were referring to v3 from .
But I see the v4 you posted below, which I picked up.
prev parent reply other threads:[~2022-11-13 5:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 23:12 What's cooking in git.git (Nov 2022, #02; Tue, 8) Taylor Blau
2022-11-10 21:35 ` Jeff King
2022-11-11 2:42 ` Taylor Blau
2022-11-12 14:40 ` Philip Oakley
2022-11-13 5:05 ` Taylor Blau
2022-11-13 5:08 ` Taylor Blau [this message]
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).