* When to resend a patchset?
@ 2015-07-18 14:11 Ricardo Ribalda Delgado
2015-07-19 18:46 ` Greg KH
0 siblings, 1 reply; 3+ messages in thread
From: Ricardo Ribalda Delgado @ 2015-07-18 14:11 UTC (permalink / raw)
To: kernelnewbies
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?
Anything better than the lwn?
I dont want to wast useful maintainer time :)
Thanks!
--
Ricardo Ribalda
^ permalink raw reply [flat|nested] 3+ messages in thread
* When to resend a patchset?
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
0 siblings, 1 reply; 3+ messages in thread
From: Greg KH @ 2015-07-19 18:46 UTC (permalink / raw)
To: kernelnewbies
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 :)
^ permalink raw reply [flat|nested] 3+ messages in thread
* When to resend a patchset?
2015-07-19 18:46 ` Greg KH
@ 2015-07-19 18:51 ` Robert P. J. Day
0 siblings, 0 replies; 3+ messages in thread
From: Robert P. J. Day @ 2015-07-19 18:51 UTC (permalink / raw)
To: kernelnewbies
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
========================================================================
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-07-19 18:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).