All of lore.kernel.org
 help / color / mirror / Atom feed
From: bjorn@mork.no (Bjørn Mork)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Wait times for patch submission
Date: Tue, 06 Jan 2015 21:29:44 +0100	[thread overview]
Message-ID: <87k30zps93.fsf@nemi.mork.no> (raw)
In-Reply-To: <CAC+QLdT-8LeYdRGHsjpYjY-HByb+b6Ty6f=WHLw2JWhc8pSi3A@mail.gmail.com> (Mandeep Sandhu's message of "Tue, 6 Jan 2015 11:31:53 -0800")

Mandeep Sandhu <mandeepsandhu.chd@gmail.com> writes:

> Hi All,
>
> I wanted to check with ppl who frequently post patches to LKML on how
> long should one should wait before resending the patches in case
> there's no response to them.

That depends on lots of factors.  Like how important the patch is, what
kind of patch management system the maintainer uses, etc, etc.

> I had sent a patch on Greg KH's staging-next tree, on 16 Dec '14 to
> LKML and the relevant maintainers.
>
> I got a mail from Greg's friendly bot stating that the branch was
> closed and that the patches will be looked at once the merge window
> closes.

Which usually (always?) is true.  Note that "once the merge window
closes" doesn't necessarily mean within days after -rc1.  It might mean
a few weeks if the maintainer is busy doing other stuff, like travelling
etc.  And maintainers are always busy :-)

Some maintainers even have a life, which implies taking time off with
their family at this time of the year.  You should therefore give them a
week or two extra slack.

And no, this does not count as "no response".  You got a reply giving a
precise description of how your patches will be handled and what you
need to do.

> Do I need to resend the patches again or will they be picked up from
> the maintainer's queue?

They will most likely be picked up as promised, and you'll get another
mail telling you which tree they were added to.

I would wait until at least -rc5 in any case before considering a
repost of something destined for the next release. That still leaves
plenty of time before the next merge window opens.


Bj?rn

  parent reply	other threads:[~2015-01-06 20:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 19:31 Wait times for patch submission Mandeep Sandhu
2015-01-06 20:24 ` Greg KH
2015-01-06 21:24   ` Mandeep Sandhu
2015-01-06 22:12     ` Greg KH
2015-01-06 22:31       ` Mandeep Sandhu
2015-01-06 20:29 ` Bjørn Mork [this message]
2015-01-06 21:26   ` Mandeep Sandhu

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=87k30zps93.fsf@nemi.mork.no \
    --to=bjorn@mork.no \
    --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.