DPDK patches and discussions
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/4] doc: move tool guides in their own subdirectory
Date: Mon, 26 Sep 2016 18:16:18 +0200	[thread overview]
Message-ID: <CAATJJ0KUFSHBtpDa76d-hmhiibU_2fNYt71cjBJ9bJnVLj=6ag@mail.gmail.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE202622F0E@IRSMSX103.ger.corp.intel.com>

On Mon, Sep 26, 2016 at 5:13 PM, Mcnamara, John <john.mcnamara@intel.com>
wrote:

>
> P.S. Could you mark the V1 version as "superseded" in PatchWork.


Done

I'd have thought it does that automatically.
But maybe it failed to identify them as belonging together.

Thanks for the hint - cleanup is always good.


-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

  reply	other threads:[~2016-09-26 16:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 11:16 [dpdk-dev] [PATCH 0/4] provide man pages for binaries provided by DPDK Christian Ehrhardt
2016-08-04 11:16 ` [dpdk-dev] [PATCH 1/4] doc: rendering and installation of man pages Christian Ehrhardt
2016-08-30 14:52   ` Mcnamara, John
2016-08-04 11:16 ` [dpdk-dev] [PATCH 2/4] doc: add basic invocation info for dpdk-pmdinfo Christian Ehrhardt
2016-08-30 14:59   ` Mcnamara, John
2016-08-31  7:29     ` Christian Ehrhardt
2016-08-04 11:16 ` [dpdk-dev] [PATCH 3/4] doc: add basic invocation info for dpdk-devbind Christian Ehrhardt
2016-08-30 15:05   ` Mcnamara, John
2016-08-31  7:47     ` Christian Ehrhardt
2016-08-04 11:16 ` [dpdk-dev] [PATCH 4/4] doc: make the devbind man page be part of section 8 Christian Ehrhardt
2016-08-30 15:12   ` Mcnamara, John
2016-08-31  6:45     ` Christian Ehrhardt
2016-08-30 14:51 ` [dpdk-dev] [PATCH 0/4] provide man pages for binaries provided by DPDK Mcnamara, John
2016-08-31  5:54   ` Panu Matilainen
2016-08-31  6:46     ` Christian Ehrhardt
2016-08-31  7:50       ` [dpdk-dev] [PATCH v2 " Christian Ehrhardt
2016-08-31  7:50         ` [dpdk-dev] [PATCH v2 1/4] doc: move tool guides in their own subdirectory Christian Ehrhardt
2016-09-26 15:13           ` Mcnamara, John
2016-09-26 16:16             ` Christian Ehrhardt [this message]
2016-08-31  7:50         ` [dpdk-dev] [PATCH v2 2/4] doc: rendering and installation of man pages Christian Ehrhardt
2016-09-26 15:14           ` Mcnamara, John
2016-10-26 21:13           ` Thomas Monjalon
2016-08-31  7:50         ` [dpdk-dev] [PATCH v2 3/4] doc: add basic invocation info for dpdk-pmdinfo Christian Ehrhardt
2016-09-26 15:14           ` Mcnamara, John
2016-08-31  7:50         ` [dpdk-dev] [PATCH v2 4/4] doc: add basic invocation info for dpdk-devbind Christian Ehrhardt
2016-09-26 15:15           ` Mcnamara, John
2016-09-14 11:58         ` [dpdk-dev] [PATCH v2 0/4] provide man pages for binaries provided by DPDK Luca Boccassi
2016-10-26 21:32           ` 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='CAATJJ0KUFSHBtpDa76d-hmhiibU_2fNYt71cjBJ9bJnVLj=6ag@mail.gmail.com' \
    --to=christian.ehrhardt@canonical.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@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 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).