All of lore.kernel.org
 help / color / mirror / Atom feed
From: Panu Matilainen <pmatilai@redhat.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/2] Provide reasonable default to -n
Date: Tue, 27 Oct 2015 09:19:24 +0200	[thread overview]
Message-ID: <562F257C.9050504@redhat.com> (raw)
In-Reply-To: <1823202.buTM6Lohp1@xps13>

On 10/26/2015 06:56 PM, Thomas Monjalon wrote:
> Panu,
> Please use --subject-prefix 'PATCH v2' to ease patch management,
> as explained here:
> 	http://dpdk.org/dev#send
>
> git send-email --subject-prefix 'PATCH vX+1' --annotate --cover-letter --in-reply-to <vX-email-id>
>
> It should appear on the cover letter and the patches.

Oh, I thought I was doing it by the book but apparently not so.
Apologies, I'll fix my ways.

	- Panu -

      reply	other threads:[~2015-10-27  7:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 10:22 [PATCH] eal: default to one memory channel if not specified Panu Matilainen
2015-10-14 11:45 ` David Marchand
2015-10-14 12:04   ` Panu Matilainen
2015-10-14 13:05     ` Bruce Richardson
2015-10-15 11:49 ` [PATCH 0/2] Provide reasonable default to -n Panu Matilainen
2015-10-15 11:49   ` [PATCH 1/2] mempool: use a better default for number of memory channels Panu Matilainen
2015-10-15 11:49   ` [PATCH 2/2] eal: make the -n argument optional Panu Matilainen
2015-10-15 12:03   ` [PATCH 0/2] Provide reasonable default to -n David Marchand
2015-10-26 16:51     ` Thomas Monjalon
2015-10-15 12:10   ` Mcnamara, John
2015-10-15 12:36     ` Panu Matilainen
2015-10-15 13:12       ` Mcnamara, John
2015-10-26 16:50         ` Thomas Monjalon
2015-10-26 16:56   ` Thomas Monjalon
2015-10-27  7:19     ` Panu Matilainen [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=562F257C.9050504@redhat.com \
    --to=pmatilai@redhat.com \
    --cc=dev@dpdk.org \
    --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.