DPDK website maintenance
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>
Cc: "web@dpdk.org" <web@dpdk.org>, nd <nd@arm.com>,
	Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Subject: Re: [dpdk-web] [PATCH] update patch submission process
Date: Tue, 30 Jun 2020 17:39:54 +0000	[thread overview]
Message-ID: <DB6PR0802MB2216F4C0DE0ED214B3AEBFB4986F0@DB6PR0802MB2216.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <12147920.4rO7tnnPZT@thomas>

<snip>
> 30/06/2020 17:49, Honnappa Nagarahalli:
> > > --- a/content/contribute/_index.md
> > > +++ b/content/contribute/_index.md
> > > @@ -57,6 +57,13 @@ The email title must begin with *[PATCH]* to
> > > distinguish it among discussions.
> > >  There must be details in the commit log, explaining what was the
> > > problem and how it is fixed.\  When fixing a regression, it is a
> > > good idea to reference the id of  the commit which introduced the bug
> (see fixline alias below).
> >
> > I believe we are supposed to add the author of the commit also in 'Cc' tag. Is
> this correct?
> 
> Yes
> Should it be added in this short summary?
> Any idea about a short wording?
I think we can skip the wording. Instead add the following:
Cc: author@example.com

> 
> 


      reply	other threads:[~2020-06-30 17:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30  8:58 Thomas Monjalon
2020-06-30  9:03 ` Andrew Rybchenko
2020-06-30 15:49 ` Honnappa Nagarahalli
2020-06-30 16:19   ` Thomas Monjalon
2020-06-30 17:39     ` Honnappa Nagarahalli [this message]

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=DB6PR0802MB2216F4C0DE0ED214B3AEBFB4986F0@DB6PR0802MB2216.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=nd@arm.com \
    --cc=thomas@monjalon.net \
    --cc=web@dpdk.org \
    /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;
as well as URLs for NNTP newsgroup(s).