All of lore.kernel.org
 help / color / mirror / Atom feed
From: me@tobin.cc (Tobin C. Harding)
To: kernelnewbies@lists.kernelnewbies.org
Subject: patch protocol question
Date: Wed, 8 Mar 2017 08:29:10 +1100	[thread overview]
Message-ID: <20170307212910.GH10714@eros> (raw)

I would like to know the correct protocol in order to make the
maintainers job as easy as possible please. 

Once a patch has been reviewed and the review makes good points that
mean the patch is invalid/unnecessary what is the protocol from then?
Assuming one replies to the reviewer with thanks and acknowledging
their points. Is it then protocol to state that you are not going to
pursue the patch further? How do maintainers know to not bother any
more with a patch?

Similar question; if the last patch of a patch series is not needed
should one resend another version without the last patch or is there
an accepted protocol to signal this so that the maintainer only looks
at merging the initial patches in the series.

thanks,
Tobin.

             reply	other threads:[~2017-03-07 21:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 21:29 Tobin C. Harding [this message]
2017-03-07 23:12 ` patch protocol question Peter Senna Tschudin
2017-03-08  3:56   ` Tobin C. Harding

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=20170307212910.GH10714@eros \
    --to=me@tobin.cc \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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.