From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: When to resend a patchset?
Date: Sun, 19 Jul 2015 14:51:50 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1507191450480.2446@localhost> (raw)
In-Reply-To: <20150719184650.GB9565@kroah.com>
On Sun, 19 Jul 2015, Greg KH wrote:
> On Sat, Jul 18, 2015 at 04:11:30PM +0200, Ricardo Ribalda Delgado wrote:
> > Hello
> >
> > Usually I was taking the approach of pinging a patch after 21 days of
> > inactivity.
> >
> > This has worked ok in the past, but the last time I have done it I
> > was told that the merge window was open and that nothing could be done
> > at that time.
> >
> > Is there a written guideline to know when to resend/ping a patch?
> > How can I figure out the current development status of the kernel?
>
> Look at the release that is happening this week, that will tell you
> the status. Take a look at Documentation/development_process/ for
> more details than you ever wanted to know :)
it's just eerie how any discussion involving greg KH typically ends
with the phrase, "more details than you ever wanted to know." :-)
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2015-07-19 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 14:11 When to resend a patchset? Ricardo Ribalda Delgado
2015-07-19 18:46 ` Greg KH
2015-07-19 18:51 ` Robert P. J. Day [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=alpine.LFD.2.20.1507191450480.2446@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).