From: "Laszlo Ersek" <lersek@redhat.com>
To: Philippe Mathieu-Daude <philmd@redhat.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
devel@edk2.groups.io
Cc: Bob Feng <bob.c.feng@intel.com>, Liming Gao <liming.gao@intel.com>
Subject: Re: [PATCH 0/3] BaseTools: Add a script to use with 'git-send-email --cc-cmd'
Date: Wed, 16 Oct 2019 16:49:05 +0200 [thread overview]
Message-ID: <b2584c76-819e-dce1-5686-48f3d8a3f118@redhat.com> (raw)
In-Reply-To: <20191016140940.18844-1-philmd@redhat.com>
Hi Phil,
On 10/16/19 16:09, Philippe Mathieu-Daude wrote:
> Hi,
>
> This series contains trivial fixes to the GetMaintainer.py script,
> then adds a new script which allow git-send-email to automatically
> fills the email addresses relevant to each patch, using the new
> Maintainer.txt format (with the GetMaintainer.py script).
>
> I sent this series adding:
>
> [sendemail]
> ccCmd = /home/phil/source/edk2/BaseTools/Scripts/GitCcCmd.sh
>
> To my /home/phil/source/edk2/.git/config
>
> The sendemail.ccCmd entry is documented here:
> https://git-scm.com/docs/git-send-email#Documentation/git-send-email.txt---cc-cmdltcommandgt
I'm neutral on this patch set; I defer to Leif and others for reviewing it.
I like to rely on explicit Cc: tags in the commit messages, and those
tags only. They give me better per-patch control, they work nicely
across rebases, and I like to see them in the git commit history too.
Furthermore, if someone else takes over a patch from a pending series,
for a rework, they get the Cc's too. If a reviewer expresses permanent
uninterest in a patch, I can drop them permanently.
That said, I don't mind if others use "sendemail.ccCmd"!
Thanks,
Laszlo
next prev parent reply other threads:[~2019-10-16 14:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 14:09 [PATCH 0/3] BaseTools: Add a script to use with 'git-send-email --cc-cmd' Philippe Mathieu-Daudé
2019-10-16 14:09 ` [PATCH 1/3] BaseTools: Let the GetMaintainer.py script be executable Philippe Mathieu-Daudé
2019-10-18 1:44 ` Bob Feng
2019-10-16 14:09 ` [PATCH 2/3] BaseTools: Add '--quiet' option to GetMaintainer.py script Philippe Mathieu-Daudé
2019-10-16 14:09 ` [PATCH 3/3] BaseTools: Add script to help git-send-email pick addresses to cc Philippe Mathieu-Daudé
2019-10-16 14:12 ` Philippe Mathieu-Daudé
2019-10-16 14:49 ` Laszlo Ersek [this message]
2019-10-16 15:18 ` [PATCH 0/3] BaseTools: Add a script to use with 'git-send-email --cc-cmd' Leif Lindholm
2019-10-16 16:50 ` Philippe Mathieu-Daudé
2019-10-16 18:30 ` Stefan Hajnoczi
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-list 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=b2584c76-819e-dce1-5686-48f3d8a3f118@redhat.com \
--to=devel@edk2.groups.io \
/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