From: Jeff King <peff@peff.net>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC for GIT] pull-request: add praise to people doing QA
Date: Thu, 19 Jan 2017 16:20:40 -0500 [thread overview]
Message-ID: <20170119212039.3gixsrk7qco45wjo@sigill.intra.peff.net> (raw)
In-Reply-To: <20170119204343.xtotmjddhbum2mvr@ninjato>
On Thu, Jan 19, 2017 at 09:43:45PM +0100, Wolfram Sang wrote:
> > As to the implementation, I am wondering if we can make this somehow
> > work well with the "trailers" code we already have, instead of
> > inventing yet another parser of trailers.
> >
> > In its current shape, "interpret-trailers" focuses on "editing" an
> > existing commit log message to tweak the trailer lines. That mode
> > of operation would help amending and rebasing, and to do that it
> > needs to parse the commit log message, identify trailer blocks,
> > parse out each trailer lines, etc.
> >
> > There is no fundamental reason why its output must be an edited
> > original commit log message---it should be usable as a filter that
> > picks trailer lines of the selected trailer type, like "Tested-By",
> > etc.
>
> I didn't know about trailers before. As I undestand it, I could use
> "Tested-by" as the key, and the commit subject as the value. This list
> then could be parsed and brought into proper output shape. It would
> simplify the subject parsing, but most things my AWK script currently
> does would still need to stay or to be reimplemented (extracting names
> from tags, creating arrays of tags given by $name). Am I correct?
>
> All under the assumption that trailers work on a range of commits. I
> have to admit that adding this to git is beyond my scope.
This sounds a lot like the shortlog-trailers work I did about a year
ago:
http://public-inbox.org/git/20151229073832.GN8842@sigill.intra.peff.net/
http://public-inbox.org/git/20151229075013.GA9191@sigill.intra.peff.net/
Nobody seemed to really find it useful, so I didn't pursue it.
Some of the preparatory patches in that series bit-rotted in the
meantime, but you can play with a version based on v2.7.0 by fetching
the "shortlog-trailers-historical" branch from
https://github.com/peff/git.git.
And then things like:
git shortlog --ident=tested-by --format='...tested a patch by %an'
work (and you can put whatever commit items you want into the --format,
including just dumping the hash if you want to do more analysis).
-Peff
next prev parent reply other threads:[~2017-01-19 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 18:30 [RFC for GIT] pull-request: add praise to people doing QA Wolfram Sang
2017-01-16 0:35 ` Junio C Hamano
2017-01-16 4:05 ` Jacob Keller
2017-01-19 20:43 ` Wolfram Sang
2017-01-19 21:20 ` Jeff King [this message]
2017-01-19 23:42 ` Jacob Keller
2017-01-20 0:06 ` Joe Perches
2017-01-20 0:13 ` Jacob Keller
2017-01-19 21:22 ` Junio C Hamano
2017-01-19 22:02 ` Wolfram Sang
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=20170119212039.3gixsrk7qco45wjo@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).