[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081119081359.GB794@linux-mips.org>
Date: Wed, 19 Nov 2008 08:13:59 +0000
From: Ralf Baechle <ralf@...ux-mips.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Linux/m68k <linux-m68k@...r.kernel.org>,
David Woodhouse <dwmw2@...radead.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Kernel Development <linux-kernel@...r.kernel.org>,
linux-next@...r.kernel.org
Subject: Re: linux-m68k.git
On Tue, Nov 18, 2008 at 09:49:01PM +0100, Geert Uytterhoeven 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.
>
> As suggested by David Woodhouse, I grouped the commits by topic. But unlike
> David's suggestion, I used topic branches, not topic repositories. Oh well,
> we'll see...
That's easy enough to undo if the need should arise.
> I also created for-next and for-linus branches. Do they look OK?
>
> If I did something wrong, please let me know.
> This is still experimental stuff, which may be rebased if needed.
>
> In addition, one day I may pull from Ralf's repository that reflects the state
> of Linux/m68k CVS a few commits before our server died...
It's CVS that must die, not the poor server ;-) If you're actually going
to pull the old CVS stuff into the new git repository and you happen to have
a newer snapshot than the one which I've converted I can re-run my converter.
Ralf
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists