From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: What can I do if I sent a wrong patch?
Date: Sun, 19 Jul 2015 05:46:20 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1507190544150.26267@localhost> (raw)
In-Reply-To: <20150719094020.GA1992@debian>
On Sun, 19 Jul 2015, Navy wrote:
> Hello,
> A mistake was found after I sent the patch to mentors. What Can I do
> to make up the fault?
first, if they're truly mentors, they should check the patch
themselves and catch the error. otherwise, they're not really doing
their job as "mentors."
second, you need to self-examine what you failed to do properly to
have sent in a bad patch.
i doubt you've done any real harm; the linux kernel has lots of
checking up the hierarchy so that a truly damaging patch is rarely
going to get into the source tree.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2015-07-19 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 9:40 What can I do if I sent a wrong patch? Navy
2015-07-19 9:46 ` Robert P. J. Day [this message]
2015-07-19 21:03 ` Rik van Riel
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=alpine.LFD.2.20.1507190544150.26267@localhost \
--to=rpjday@crashcourse.ca \
--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 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).