All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, david.marchand@redhat.com,
	john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc: add Vhost and Virtio updates to release note
Date: Thu, 01 Oct 2020 23:33:10 +0200	[thread overview]
Message-ID: <2715653.HrAAcl6WpO@thomas> (raw)
In-Reply-To: <3759283.WSBrEPX1tx@thomas>

01/10/2020 14:53, Thomas Monjalon:
> 01/10/2020 13:45, Maxime Coquelin:
> > 
> > On 10/1/20 1:42 PM, Thomas Monjalon wrote:
> > > 01/10/2020 12:36, Maxime Coquelin:
> > >> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> > >> ---
> > >>  doc/guides/rel_notes/release_20_11.rst | 10 ++++++++++
> > >>  1 file changed, 10 insertions(+)
> > > 
> > > Those changes should have been part of the original commits.
> > > Please can you add the "Fixes:" lines so we can have an easy
> > > reference to the code change?
> > 
> > I'm not convinced it is a good idea, as it creates avoidable conflicts
> > when someone wants to backport features.
> 
> Not sure I understand the conflict you think of.
> 
> > But if you insist I can do it.

I did the release notes updates in the relevant patches
while pulling next-net.
I've removed the deprecation notice as well.



  reply	other threads:[~2020-10-01 21:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 10:36 [dpdk-dev] [PATCH] doc: add Vhost and Virtio updates to release note Maxime Coquelin
2020-10-01 11:42 ` Thomas Monjalon
2020-10-01 11:45   ` Maxime Coquelin
2020-10-01 12:53     ` Thomas Monjalon
2020-10-01 21:33       ` Thomas Monjalon [this message]
2020-10-01 21:41         ` Maxime Coquelin

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=2715653.HrAAcl6WpO@thomas \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=maxime.coquelin@redhat.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.