From: Ralf Baechle <ralf@linux-mips.org>
To: Markos Chandras <Markos.Chandras@imgtec.com>
Cc: linux-mips@linux-mips.org
Subject: Re: MIPS in 3.19
Date: Fri, 12 Dec 2014 15:22:33 +0100 [thread overview]
Message-ID: <20141212142232.GA11185@linux-mips.org> (raw)
In-Reply-To: <548AB1B8.7040503@imgtec.com>
On Fri, Dec 12, 2014 at 09:13:28AM +0000, Markos Chandras wrote:
> I am a little confused as well. Sometimes the pull requests appear on
> LMO, some other times they don't. Would it be possible to CC LMO every
> time a pull request is sent to Linus so we have time to review it (more
> pair of eyes is not a bad thing) and comment on it if needed?
I only recently started cc'ing the list so forgive if I sometimes forget.
In this particular case however not cc'ing was intionsional because I
sent out the list of patches minutes after the pull request in the email
that started this thread.
While it is possible to look at what's pending for Linus in upstream-sfr
at any time, not a whole lot of people seem to do that and maybe I should
make it a habit to post a list of what's pending by -rc5 or -rc6 by which
time there is still time for some last minute changes.
That said, already a few releases ago I started to enforce the rc5
deadline for accepting major submission - with a few smaller exceptions,
based on the assessed risk. But this time the volume of patches forced
me to be more radical or I'd probably still be shifting patches around!
Now, Linus has pulled. Let's sort the mess than move on to 3.20 ...
Ralf
prev parent reply other threads:[~2014-12-12 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 13:27 MIPS in 3.19 Ralf Baechle
2014-12-11 19:19 ` Kevin Cernekee
2014-12-11 21:22 ` Ralf Baechle
2014-12-12 1:54 ` Florian Fainelli
2014-12-12 9:13 ` Markos Chandras
2014-12-12 9:13 ` Markos Chandras
2014-12-12 14:22 ` Ralf Baechle [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=20141212142232.GA11185@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Markos.Chandras@imgtec.com \
--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 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.