From: Dinh Nguyen <dinguyen@altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [OT] CC:s in commits (was: [PATCH 1/2] socfpga: Adding Scan Manager driver)
Date: Mon, 13 Jan 2014 15:14:58 -0600 [thread overview]
Message-ID: <1389647698.10673.3.camel@linux-builds1> (raw)
In-Reply-To: <20140113210815.2724A3821F6@gemini.denx.de>
Hi Wolfgang,
On Mon, 2014-01-13 at 22:08 +0100, ZY - wd wrote:
> Dear Albert,
>
> In message <20140113173924.684ce548@lilith> you wrote:
> >
> > > Actually these Cc will be helpful when using git send-email. It will
> > > auto cc to these mailing list when the patch is send out for review
> > > (instead entering the names manually every time). Thanks
> >
> > That is useful to the sender, but useless to anyone else.
>
> This is not correct. It is also an indicatioin who was explicitly
> addressed when the patch was submitted, so you can later still see
> from the commit message who was invited to commend and refrained from
> doing so. This may help a lot in discussions like "but I never had a
> chance to see this patch".
>
> Please keep these. The are really useful.
I'm glad you weighed in on this. I have done this CC: field many times
in patches sent to kernel.org, and have not received any feedbacks to
remove it. Some patches can include quite a few entries. So I was kinda
surprised to see a comment about it here on the u-boot list.
Dinh
>
> Best regards,
>
> Wolfgang Denk
>
next prev parent reply other threads:[~2014-01-13 21:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 17:34 [U-Boot] [PATCH 1/2] socfpga: Adding Scan Manager driver Chin Liang See
2014-01-13 8:34 ` [U-Boot] [OT] CC:s in commits (was: [PATCH 1/2] socfpga: Adding Scan Manager driver) Albert ARIBAUD
2014-01-13 14:34 ` Chin Liang See
2014-01-13 16:39 ` Albert ARIBAUD
2014-01-13 17:41 ` Chin Liang See
2014-01-13 21:09 ` Wolfgang Denk
2014-01-13 22:20 ` Chin Liang See
2014-01-13 21:08 ` Wolfgang Denk
2014-01-13 21:14 ` Dinh Nguyen [this message]
2014-01-13 22:07 ` Albert ARIBAUD
2014-01-13 22:20 ` Chin Liang See
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=1389647698.10673.3.camel@linux-builds1 \
--to=dinguyen@altera.com \
--cc=u-boot@lists.denx.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