From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hurd <stephen.hurd@broadcom.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Updates to large patchsets
Date: Thu, 12 May 2016 09:43:48 +0200 [thread overview]
Message-ID: <4079874.Szl0fMNbYL@xps13> (raw)
In-Reply-To: <CAJ9nmBa7doV9Lm6ZRYEikKY0tjsD40Gp_UOeMEFYJzH_Jtv6Cw@mail.gmail.com>
2016-05-11 14:22, Stephen Hurd:
> When submitting an update to a single patch in a large patchset, what's the
> preferred method? Do I send a single "[PATCH v2 01/40]" email with the
> modified patch or do I send the entire series of 40 patches again?
Good question :)
It's generally easier to understand if the whole series is sent.
If the series is large, it is better to wait to have several changes.
If you are almost sure there will be no more change except 1 or 2 small
ones, then you can send only these single patches.
Anyway, please keep patchwork status updated, i.e. mark old patches as
superseded.
prev parent reply other threads:[~2016-05-12 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 21:22 Stephen Hurd
2016-05-12 7:43 ` Thomas Monjalon [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=4079874.Szl0fMNbYL@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=stephen.hurd@broadcom.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).