docs: netdev: rephrase the 'should I update patchwork' question
Make the question shorter and adjust the start of the answer accordingly. Signed-off-by: Jakub Kicinski <kuba@kernel.org> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
This commit is contained in:
parent
8f785c1bb8
commit
724c1a7443
|
@ -125,9 +125,11 @@ Asking the maintainer for status updates on your
|
||||||
patch is a good way to ensure your patch is ignored or pushed to the
|
patch is a good way to ensure your patch is ignored or pushed to the
|
||||||
bottom of the priority list.
|
bottom of the priority list.
|
||||||
|
|
||||||
I submitted multiple versions of the patch series. Should I directly update patchwork for the previous versions of these patch series?
|
Should I directly update patchwork state of my own patches?
|
||||||
--------------------------------------------------------------------------------------------------------------------------------------
|
-----------------------------------------------------------
|
||||||
No, please don't interfere with the patch status on patchwork, leave
|
It may be tempting to help the maintainers and update the state of your
|
||||||
|
own patches when you post a new version or spot a bug. Please do not do that.
|
||||||
|
Interfering with the patch status on patchwork will only cause confusion. Leave
|
||||||
it to the maintainer to figure out what is the most recent and current
|
it to the maintainer to figure out what is the most recent and current
|
||||||
version that should be applied. If there is any doubt, the maintainer
|
version that should be applied. If there is any doubt, the maintainer
|
||||||
will reply and ask what should be done.
|
will reply and ask what should be done.
|
||||||
|
|
Loading…
Reference in New Issue