From: Chin Liang See <clsee@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 08:34:36 -0600 [thread overview]
Message-ID: <1389623676.9282.4.camel@clsee-VirtualBox.altera.com> (raw)
In-Reply-To: <20140113093439.1b2a47f4@lilith>
Dear Albert,
On Mon, 2014-01-13 at 09:34 +0100, ZY - albert.u.boot wrote:
> On Wed, 13 Nov 2013 11:34:10 -0600, Chin Liang See <clsee@altera.com>
> wrote:
>
> > Scan Manager driver will be called to configure the IOCSR
> > scan chain. This configuration will setup the IO buffer settings
> >
> > Signed-off-by: Chin Liang See <clsee@altera.com>
> > Cc: Dinh Nguyen <dinguyen@altera.com>
> > Cc: Wolfgang Denk <wd@denx.de>
> > CC: Pavel Machek <pavel@denx.de>
> > Cc: Tom Rini <trini@ti.com>
> > Cc: Albert Aribaud <albert.u.boot@aribaud.net>
> > ---
>
> Not sure what the point is of these CC:s in the commit message. Do I
> miss some use of these? Can I, should I, should I not remove them
> from the commit when applying to my tree?
>
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
Chin Liang
> Amicalement,
next prev parent reply other threads:[~2014-01-13 14:34 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 [this message]
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
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=1389623676.9282.4.camel@clsee-VirtualBox.altera.com \
--to=clsee@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