[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMuHMdWJPOvrU62GuN4-3+61V5kvaPZ40g5LkqzMp5dGnK+_+w@mail.gmail.com>
Date: Sun, 13 Nov 2011 11:44:56 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: "Linux/m68k" <linux-m68k@...r.kernel.org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: linux-m68k.git is back
On Thu, Oct 13, 2011 at 09:22, Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> linux-m68k.git is back, in the usual place:
>
> http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git
>
> Interesting branches:
> - master: main development, containing accepted changesets,
> - m68k-queue: (almost) identical to master, but nice changesets rebased on top of
> the latest v* tag (incl. release candidates) from Linus (I don't follow stable),
I added the following cleanups to master:
m68k: Remove unused platform.c skeleton files
m68k: Remove unused GVP IO-Extender files and config symbols
m68k: Remove unused mc68681.h header file for MultiFace III serial
fs/fat: Reorder options to match the m68k-queue branch
m68k/atari: Remove Atari SCC serial driver
Revert "CONFIG_SWAP=n: include/linux/swap.h needs <linux/pagemap.h>"
m68k/atari: Remove superfluous comment in debug code
and now it's identical to m68k-queue. I'll keep it that way.
> - for-*: What's destined for a specific merge window. The latest overlap with
> for-linus/for-next,
Sometimes they may be a few commits ahead of for-linus/for-next, e.g. if
those commits have to go in through another maintainer's tree.
> master and m68k-v* are never rebased. m68k-queue and for-* are rebased when a
> new v* comes out.
and they may be reshuffled when commits are added.
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