[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0811182136060.27671@anakin>
Date: Tue, 18 Nov 2008 21:49:01 +0100 (CET)
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Linux/m68k <linux-m68k@...r.kernel.org>
cc: Ralf Baechle <ralf@...ux-mips.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: linux-m68k.git
(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...
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...
Thanks for all your (past and future) help, suggestions, tips and tricks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
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