Re: When to resend a patchset?

2015-07-19 Thread Robert P. J. Day
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


___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: When to resend a patchset?

2015-07-19 Thread Greg KH
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 :)

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


When to resend a patchset?

2015-07-18 Thread Ricardo Ribalda Delgado
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

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies