From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Yoshinori Sato <ysato@users•sourceforge.jp>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: bad base of the h8300 tree
Date: Sat, 3 Oct 2015 14:28:38 +1000 [thread overview]
Message-ID: <20151003142838.4bcd9570@canb.auug.org.au> (raw)
In-Reply-To: <87vbappzob.wl-ysato@users.sourceforge.jp>
Hi Yoshinori,
On Fri, 02 Oct 2015 15:11:48 +0900 Yoshinori Sato <ysato@users•sourceforge.jp> wrote:
>
> On Tue, 15 Sep 2015 08:12:01 +0900,
> Stephen Rothwell wrote:
> >
> > On Tue, 15 Sep 2015 09:10:30 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> > >
> > > Please do "gitk 9751a9e449da..h8300-next" in your tree and look at
> > > it (9751a9e449da is in Linus' tree). As I suggested above, maybe you
> > > should go back to commit 99bcfda85f66 and work forward from there
> > > (after amending it have a SOB). Or just start all over with v4.3 ...
> >
> > I meant v4.3-rc1, of course.
>
> OK.
> fixed it.
Well, not really :-(
It is now based on next-20150925. As I have said before, you cannot
base your linux-next included branch on a linux-next release. You
should either base it on Linus' tree, or one of the other linux-next
included branches (as long as that other branch is never rebased).
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
next prev parent reply other threads:[~2015-10-03 4:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 21:43 linux-next: bad base of the h8300 tree Stephen Rothwell
2015-08-31 21:40 ` Stephen Rothwell
2015-09-13 23:54 ` Stephen Rothwell
2015-09-14 23:10 ` Stephen Rothwell
2015-09-14 23:12 ` Stephen Rothwell
2015-10-02 6:11 ` Yoshinori Sato
2015-10-03 4:28 ` Stephen Rothwell [this message]
2015-10-14 22:21 ` Stephen Rothwell
2015-10-19 21:57 ` Stephen Rothwell
2015-10-20 4:28 ` Yoshinori Sato
2015-10-20 20:42 ` Stephen Rothwell
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=20151003142838.4bcd9570@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=ysato@users$(echo .)sourceforge.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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