From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: rebase of the h8300-remove tree
Date: Wed, 4 Sep 2013 17:12:07 -0700 [thread overview]
Message-ID: <20130905001207.GA16300@roeck-us.net> (raw)
In-Reply-To: <20130905095657.a3d9b1d461295bdd02efe0ec@canb.auug.org.au>
On Thu, Sep 05, 2013 at 09:56:57AM +1000, Stephen Rothwell wrote:
> Hi Guenter,
>
> Why did you bother rebasing the h8300-remove tree? None of the patches
> changed at all (not that that would matter).
>
Just wanted it based on v3.11. But you are right, it was unnecessary.
Won't happen again.
Note that I don't plan to send it to Linus in this commit window.
I thought about it, but it seems to be a bit too hasty.
Guenter
prev parent reply other threads:[~2013-09-05 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 23:56 linux-next: rebase of the h8300-remove tree Stephen Rothwell
2013-09-05 0:12 ` Guenter Roeck [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=20130905001207.GA16300@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).