All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Philip Oakley <philipoakley@iee.email>
Cc: Taylor Blau <me@ttaylorr.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2022, #01; Thu, 3)
Date: Tue, 8 Nov 2022 16:49:52 -0500	[thread overview]
Message-ID: <Y2rPAGp96IwrLS1T@nand.local> (raw)
In-Reply-To: <88b30b5f-2712-4c84-331c-2ea7338053ad@iee.email>

On Mon, Nov 07, 2022 at 12:19:22PM +0000, Philip Oakley wrote:
> On 05/11/2022 00:26, Taylor Blau wrote:
> > On Sat, Nov 05, 2022 at 12:21:23AM +0000, Philip Oakley wrote:
> >> On 04/11/2022 01:05, Taylor Blau wrote:
> >>> --------------------------------------------------
> >>> [Cooking]
> >>> * 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.
> >> Is that out of date? V3 did include tests in t4205 and t6006.
> >>
> >>>  source: <20221102120853.2013-1-philipoakley@iee.email>
> >> This source is the V3.
> > Yes, thanks for catching. Indeed, the version that I have at:
> >
> >     git@github.com:ttaylorr/git.git
> >
> > on po/pretty-hard-trunc has the new tests. I think we are still waiting
> > for review on that topic, though...
> >
> > Thanks,
> > Taylor
> An extra review would be useful.
>
> I wasn't certain about the use of `qz_to_tab_space` in the here-doc
> formulation of t6006-rev-list-format where some of the new tests now
> included trailing spaces (but others didn't).

Let's wait for a little more review before we start merging this one
down. I'll try and take a look if others don't beat me to it shortly.

Thanks,
Taylor

  reply	other threads:[~2022-11-08 21:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04  1:05 What's cooking in git.git (Nov 2022, #01; Thu, 3) Taylor Blau
2022-11-05  0:21 ` Philip Oakley
2022-11-05  0:26   ` Taylor Blau
2022-11-07 12:19     ` Philip Oakley
2022-11-08 21:49       ` Taylor Blau [this message]
2022-11-07 14:28 ` ab/config-multi-and-nonbool (was: What's cooking in git.git (Nov 2022, #01; Thu, 3)) Ævar Arnfjörð Bjarmason
2022-11-07 14:33 ` ab/make-bin-wrappers " Ævar Arnfjörð Bjarmason
2022-11-08 14:27   ` Jeff King
2022-11-08 21:52     ` Taylor Blau
2022-11-09 14:04       ` Jeff King
2022-11-07 21:14 ` ab/coccicheck-incremental " Ævar Arnfjörð Bjarmason
2022-11-08 21:53   ` Taylor Blau
2022-11-07 21:24 ` ab/sha-makefile-doc " Ævar Arnfjörð Bjarmason
2022-11-08 14:13 ` ab/submodule-helper-prep-only " Ævar Arnfjörð Bjarmason
2022-11-08 22:04   ` Taylor Blau
2022-11-08 14:14 ` ab/cmake-nix-and-ci " Ævar Arnfjörð Bjarmason
2022-11-08 14:49   ` Phillip Wood
2022-11-08 14:22 ` ab/misc-hook-submodule-run-command " Ævar Arnfjörð Bjarmason

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=Y2rPAGp96IwrLS1T@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=philipoakley@iee.email \
    /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.