From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [ANNOUNCE] Renesas branches rebased on v3.14-rc1
Date: Tue, 04 Feb 2014 12:01:29 +0000 [thread overview]
Message-ID: <20140204120129.GC17028@verge.net.au> (raw)
In-Reply-To: <20130523014003.GN22608@verge.net.au>
On Tue, Feb 04, 2014 at 09:10:13AM +0000, Ben Dooks wrote:
> On 04/02/14 06:52, Simon Horman wrote:
> >Hi,
> >
> >I have rebased the branched that include patches queued up for v3.15. The
> >new base is v3.14-rc1. I also have created new devel and next branches
> >accordingly.
> >
> >Now would be a great time to consider resending patches targeted at the
> >renesas tree which have dependencies provided by v3.14-rc1.
>
> Should I re-base and re-send items that did not make it from the last
> development cycle?
Yes, please do.
prev parent reply other threads:[~2014-02-04 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 1:40 [Announce] Renesas branches rebased on v3.10-rc2 Simon Horman
2014-02-04 6:52 ` [ANNOUNCE] Renesas branches rebased on v3.14-rc1 Simon Horman
2014-02-04 9:10 ` Ben Dooks
2014-02-04 12:01 ` Simon Horman [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=20140204120129.GC17028@verge.net.au \
--to=horms@verge.net.au \
--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;
as well as URLs for NNTP newsgroup(s).