Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1247225 > unrolled thread

Re: linux-next: bad base of the h8300 tree

Started byStephen Rothwell <sfr@canb.auug.org.au>
First post2015-10-15 00:30 +0200
Last post2015-10-15 00:30 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: linux-next: bad base of the h8300 tree Stephen Rothwell <sfr@canb.auug.org.au> - 2015-10-15 00:30 +0200

#1247225 — Re: linux-next: bad base of the h8300 tree

FromStephen Rothwell <sfr@canb.auug.org.au>
Date2015-10-15 00:30 +0200
SubjectRe: linux-next: bad base of the h8300 tree
Message-ID<qjCIy-3T7-1@gated-at.bofh.it>
Hi,

On Sat, 3 Oct 2015 14:28:38 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> 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).

OK, now your tree is no longer based on a linux-next release (thanks).
However, you have managed to rebase a whole string of post v4.3-rc5
commits from Linus' tree into your tree.  This would mean that we would
end up with duplicates of those patches.  Please just rebase your
patches (and just your patches) onto some part of Linus' tree.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web