Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org
Subject: Patch submission deadlines
Date: Thu, 13 Sep 2007 15:33:20 +0100	[thread overview]
Message-ID: <20070913143320.GB30716@linux-mips.org> (raw)

One of the things on the kernel summit was the whole patch submission.
Linus put emphasis on that he wants the pull request on the first day
of the two week merge window - and that's the pull requests from us
maintainers not those who submit to us.  As the result that means that
I won't be able able to accept any feature patches for release $n + 1
once $n has been released.

So if there is anything you want to get into 2.6.24, send asap svp.

Thanks,

  Ralf

                 reply	other threads:[~2007-09-13 14:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20070913143320.GB30716@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.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