From: Philip Oakley <email@example.com>
To: Taylor Blau <firstname.lastname@example.org>, email@example.com
Subject: Re: What's cooking in git.git (Nov 2022, #02; Tue, 8)
Date: Sat, 12 Nov 2022 14:40:56 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 08/11/2022 23:12, Taylor Blau wrote:
> * po/pretty-hard-trunc (2022-11-02) 1 commit
> - pretty-formats: add hard truncation, without ellipsis, options
> Add a new pretty format which truncates without ellipsis.
> Missing test coverage.
> source: <email@example.com>
The summary should have been updated after v3, and we were looking for
a final review <Y2rPAGp96IwrLS1T@nand.local>.
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
next prev parent reply other threads:[~2022-11-12 14:41 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 [this message]
2022-11-13 5:05 ` Taylor Blau
2022-11-13 5:08 ` Taylor Blau
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).