DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Christensen <drc@linux.vnet.ibm.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 1/4] test: fix typo in print statement
Date: Wed, 8 May 2019 15:50:44 -0700	[thread overview]
Message-ID: <17079a97-4966-fdb9-1c89-7017bc33f3a3@linux.vnet.ibm.com> (raw)
Message-ID: <20190508225044.LHyP2PiC3FpUgV9PwHX2ouNpwPMgXy7oO73lU67Sm5g@z> (raw)
In-Reply-To: <2307873.h1T1EuVh32@xps>


> It seems your emails are not threaded at all.
> It makes really hard to review them.
> All patches of a patchset must be in the same thread,
> ideally with a cover letter.
> All versions of a patchset must be in the same thread,
> ideally with the cover letter v1 being the common ancestor.
> Please check http://core.dpdk.org/contribute/#send
> 
> You need also to report the acks you got in previous versions.

I messed up with the first post in the patch series (no 0/4 message). In 
order to fix the long line problem, which post would you suggest I use 
as an anchor for my reply-to?  The original v1 1/4, the v3 1/4, or some 
other?

Dave


  parent reply	other threads:[~2019-05-08 22:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08 21:02 David Christensen
2019-05-08 21:02 ` David Christensen
2019-05-08 21:24 ` Thomas Monjalon
2019-05-08 21:24   ` Thomas Monjalon
2019-05-08 22:50   ` David Christensen [this message]
2019-05-08 22:50     ` David Christensen
2019-05-09  7:46     ` Thomas Monjalon
2019-05-09  7:46       ` Thomas Monjalon
2019-05-09 20:03       ` Thomas Monjalon
2019-05-09 20:03         ` 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=17079a97-4966-fdb9-1c89-7017bc33f3a3@linux.vnet.ibm.com \
    --to=drc@linux.vnet.ibm.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).