From: Eric Sunshine <sunshine@sunshineco.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2022, #03; Mon, 14)
Date: Mon, 14 Nov 2022 23:59:28 -0500 [thread overview]
Message-ID: <CAPig+cT-QhG+7phOYsq5WQvg9tLu3zsJrajgL=+53bEZ9ZiBNg@mail.gmail.com> (raw)
In-Reply-To: <Y3Mag8qG2D3qjlmg@nand.local>
On Mon, Nov 14, 2022 at 11:53 PM Taylor Blau <me@ttaylorr.com> wrote:
> * es/chainlint-lineno (2022-11-11) 4 commits
> - chainlint: prefix annotated test definition with line numbers
> - chainlint: latch line numbers at which each token starts and ends
> - chainlint: sidestep impoverished macOS "terminfo"
> - Merge branch 'es/chainlint-output' into es/chainlint-lineno
> (this branch uses es/chainlint-output.)
>
> Teach chainlint.pl to annotate the original test definition instead
> of the token stream.
>
> * es/chainlint-output (2022-11-08) 4 commits
> (merged to 'next' on 2022-11-14 at 9cd7d30183)
> + chainlint: annotate original test definition rather than token stream
> + chainlint: latch start/end position of each token
> + chainlint: tighten accuracy when consuming input stream
> + chainlint: add explanatory comments
> (this branch is used by es/chainlint-lineno.)
>
> Teach chainlint.pl to annotate the original test definition instead
> of the token stream.
These two topics have the same description. Perhaps the
es/chainlint-lineno topic should be described as:
Teach chainlint.pl to decorate output with line numbers.
or something.
next prev parent reply other threads:[~2022-11-15 4:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 4:50 What's cooking in git.git (Nov 2022, #03; Mon, 14) Taylor Blau
2022-11-15 4:59 ` Eric Sunshine [this message]
2022-11-15 5:01 ` Taylor Blau
2022-11-15 6:28 ` ps/receive-use-only-advertised Patrick Steinhardt
2022-11-15 6:47 ` ps/receive-use-only-advertised Taylor Blau
2022-11-15 17:28 ` ps/receive-use-only-advertised Jeff King
2022-11-16 2:02 ` ps/receive-use-only-advertised Taylor Blau
2022-11-18 23:27 ` ps/receive-use-only-advertised Junio C Hamano
2022-11-15 8:06 ` rp/maintenance-qol with 'make DEVELOPER=1' (was: What's cooking in git.git (Nov 2022, #03; Mon, 14)) Ævar Arnfjörð Bjarmason
2022-11-15 14:04 ` ms/sendemail-validate-headers, was Re: What's cooking in git.git (Nov 2022, #03; Mon, 14) Johannes Schindelin
2022-11-16 1:20 ` Taylor Blau
2022-11-16 11:48 ` Strawbridge, Michael
2022-11-18 13:24 ` Johannes Schindelin
2022-11-15 20:58 ` Eric Sunshine
2022-11-16 2:04 ` Taylor Blau
2022-11-16 6:07 ` Elijah Newren
2022-11-16 20:16 ` Taylor Blau
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
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 \
--in-reply-to='CAPig+cT-QhG+7phOYsq5WQvg9tLu3zsJrajgL=+53bEZ9ZiBNg@mail.gmail.com' \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).