[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081119081951.a1a33403.sfr@canb.auug.org.au>
Date: Wed, 19 Nov 2008 08:19:51 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Linux/m68k <linux-m68k@...r.kernel.org>,
Ralf Baechle <ralf@...ux-mips.org>,
David Woodhouse <dwmw2@...radead.org>,
Linux Kernel Development <linux-kernel@...r.kernel.org>,
linux-next@...r.kernel.org
Subject: Re: linux-m68k.git
Hi Geert,
On Tue, 18 Nov 2008 21:49:01 +0100 (CET) Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
>
> (Finally) I created an experimental git tree for Linux/m68k:
> http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git
>
> It contains more or less all patches I had in my quilt series at
> http://www.kernel.org/pub/linux/kernel/people/geert/linux-m68k-patches-2.6/
> A notable exception is m68k-PRIVATE-m68k-changes.diff, which hardcoded ARCH to
> m68k.
>
> I also created for-next and for-linus branches. Do they look OK?
They look good. I have added the for-linus branch as my m68k-current
tree and changed my m68k tree over to the for-next branch.
> If I did something wrong, please let me know.
> This is still experimental stuff, which may be rebased if needed.
That's fine as long as the commits in the for-next branch are: posted
somewhere relevant, reviewed, tested and destined for the next merge
window. (None of these requirements have changed from what should have
been in your quilt tree.)
I expect the for-linus branch to be fixes and stuff for the current
release.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists