From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
dev@dpdk.org, pablo.de.lara.guarch@intel.com,
bruce.richardson@intel.com
Subject: Re: [PATCH] devtools: check stable tag in fixes
Date: Wed, 18 Jan 2017 16:54:34 +0800 [thread overview]
Message-ID: <20170118085434.GP10293@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <21531262.6kCXYB22gk@xps13>
On Wed, Jan 18, 2017 at 09:32:22AM +0100, Thomas Monjalon wrote:
> > Yes, it's just part of the committer job, say, adding Tested-by,
> > Reviewed-by, that kind of stuff.
>
> So it should be stressed in the contribution guide that it is the
> responsibility of the author and the maintainer to put this Cc: tag.
Yes, I will do that.
> > > > Last thing, if this tag will remain in the commit log, is this only for
> > > > stable tree, or any "Cc: <mail_address>" can stay in the history?
> > >
> > > I do not see the benefit of keeping other Cc in the history.
> >
> > Again, I really don't know why you bother to remove it, manually, commit
> > by commit. What's the gain here? It just adds more burden to a committer.
> > Honestly, I never do that.
>
> I had the personal feeling that if the Cc: person is not in SoB, Ack or
> Review tags, it means he's not interested in this patch.
> After thinking more, I was probably wrong.
It's just not commonly used in DPDK, just like people here seldom use
Reviewed-by while everyone just throw an Acked-by.
> > It actually has benefits. Keeping the cc tags allows us to cc them when
> > we find a bug in that patch and make a fix patch later: they are likely
> > to want to know any follow updates on that original patch.
> >
> > It also helps when I send out a stable patch review: I send a copy to
> > all guys on the Cc list, on the Ack/Review, SoB list. I think they might
> > also want to know that patch is a candidate for a specific branch. He may
> > even give some comments, something like "if you pick this one, you might
> > want to pick another one", or "why bother to port it to a stable release",
> > that kind of thing.
>
> OK Yuanhan, thanks for the explanations.
Thanks for "listening"! :)
> I will send a v2 to relax the constraint of blank line below Fixes: tag,
> and change the warning when Cc: tag is missing. Or remove the warning?
> What do you think of: "Reminder: is it a candidate for stable@dpdk.org backport?"
Yes, I think such Reminder is enough. It might put him thinking more.
Thanks.
--yliu
next prev parent reply other threads:[~2017-01-18 8:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 14:54 [PATCH] devtools: check stable tag in fixes Thomas Monjalon
2017-01-17 18:15 ` Ferruh Yigit
2017-01-17 18:42 ` Thomas Monjalon
2017-01-18 4:41 ` Yuanhan Liu
2017-01-18 8:32 ` Thomas Monjalon
2017-01-18 8:54 ` Yuanhan Liu [this message]
2017-01-18 17:25 ` Ferruh Yigit
2017-01-19 8:05 ` Yuanhan Liu
2017-01-19 12:00 ` Ferruh Yigit
2017-01-20 7:59 ` Yuanhan Liu
2017-01-20 10:10 ` Thomas Monjalon
2017-01-20 10:23 ` Yuanhan Liu
2017-01-20 16:20 ` Ferruh Yigit
2017-01-18 9:37 ` [PATCH v2] devtools: relax tag checking " Thomas Monjalon
2017-01-18 10:04 ` Yuanhan Liu
2017-01-18 15:52 ` Thomas Monjalon
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=20170118085434.GP10293@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=thomas.monjalon@6wind.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.
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.