* [dpdk-dev] Updates to large patchsets
@ 2016-05-11 21:22 Stephen Hurd
2016-05-12 7:43 ` Thomas Monjalon
0 siblings, 1 reply; 2+ messages in thread
From: Stephen Hurd @ 2016-05-11 21:22 UTC (permalink / raw)
To: dev
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?
--
Stephen Hurd
Principal Engineer - Software Development
Broadcom Corporation
949-926-8039
stephen.hurd@broadcom.com
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [dpdk-dev] Updates to large patchsets
2016-05-11 21:22 [dpdk-dev] Updates to large patchsets Stephen Hurd
@ 2016-05-12 7:43 ` Thomas Monjalon
0 siblings, 0 replies; 2+ messages in thread
From: Thomas Monjalon @ 2016-05-12 7:43 UTC (permalink / raw)
To: Stephen Hurd; +Cc: dev
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-05-12 7:43 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-05-11 21:22 [dpdk-dev] Updates to large patchsets Stephen Hurd
2016-05-12 7:43 ` Thomas Monjalon
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).