From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [ANNOUNCE] Changes in the SH and Genesis/R-Mobile git trees
Date: Tue, 09 Nov 2010 16:26:33 +0000 [thread overview]
Message-ID: <20101109162633.GC22740@linux-sh.org> (raw)
In-Reply-To: <20101109083518.GA21086@linux-sh.org>
On Wed, Nov 10, 2010 at 02:09:50AM +1100, Stephen Rothwell wrote:
> On Tue, 9 Nov 2010 17:35:18 +0900 Paul Mundt <lethal@linux-sh.org> wrote:
> > rmobile-fixes-for-linus / sh-fixes-for-linus
> > - These are my pull branches for upstream. They will always
> > contain that which is bound for the next -rc, regardless of
> > whether we are in a merge window or late in an -rc series. They
> > will only be advanced as new things come in that need to be
> > merged in to the next -rc, and may very well stay put for
> > awhile if I've just completed a merge and all of the new
> > patches are aimed at the next kernel.
>
> Should I include these branches among my other "current" trees? These
> trees contain fixes for Linus' current -rc series and are merged very
> early in linux-next. They are in linux-next so that bugs already fixed
> are not reported again against linux-next before Linus has merged the
> fixes.
>
Oh, I hadn't even noticed those. Yes, it seems like these would be a good
fit for that. I haven't had a strict rule on rebasing for these in the
past simply because there was no immediate downstream, but I can probably
avoid that.
> I will replace the sh and genesis trees in linux-next with the above two
> branches starting with next-20101110 (and rename genesis to rmobile).
>
Great, thanks.
prev parent reply other threads:[~2010-11-09 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 8:35 [ANNOUNCE] Changes in the SH and Genesis/R-Mobile git trees Paul Mundt
2010-11-09 15:09 ` Stephen Rothwell
2010-11-09 16:26 ` Paul Mundt [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=20101109162633.GC22740@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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