From: Junio C Hamano <gitster@pobox.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC for GIT] pull-request: add praise to people doing QA
Date: Sun, 15 Jan 2017 16:35:24 -0800 [thread overview]
Message-ID: <xmqqlgubc04z.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170115183051.3565-1-wsa@the-dreams.de> (Wolfram Sang's message of "Sun, 15 Jan 2017 19:30:51 +0100")
Wolfram Sang <wsa@the-dreams.de> writes:
> === new stuff starts here
>
> with much appreciated quality assurance from
> ----------------------------------------------------------------
> Andy Shevchenko (1):
> (Rev.) i2c: piix4: Avoid race conditions with IMC
>
> Benjamin Tissoires (1):
> (Test) i2c: do not enable fall back to Host Notify by default
>
> Vladimir Zapolskiy (1):
> (Rev.) i2c: print correct device invalid address
>
> === diffstat, ...
>
> This patch is a very early RFC to collect opinions. I am not very familiar with
> the git codebase, but I guess using a filter needs to be reworked, the
> dependency on GNU awk may be frowned upon (though 'asorti' is really useful
> here), the reg-ex are not super-solid, and it should be a command-line option,
> of course. That all being said, it was a fast way to produce what I would like
> to add to my pull requests for the i2c subsystem and to see if other kernel/git
> maintainers are interested in something like this.
>
> Disclaimer: while this patch applies to the git codebase, I have to admit that
> I simply patched around in /usr/lib/git-core of my Debian machine :)
>
> So much for now, let me know what you think,
So the idea is to have list of those whose names appear on
Reviewed-by: and Tested-by: collected and listed after the list of
commit titles and author names. I personally do not see much
downsides in doing so, but I do not consume that many PRs myself, so
let's hear from those who actually do process many of them.
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.
next prev parent reply other threads:[~2017-01-16 0:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 18:30 Wolfram Sang
2017-01-16 0:35 ` Junio C Hamano [this message]
2017-01-16 4:05 ` Jacob Keller
2017-01-19 20:43 ` Wolfram Sang
2017-01-19 21:20 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqlgubc04z.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®