linux-kernel - linux-m68k.git is back

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMuHMdV4BEVPKBG7=-vvZ9fjEsaFjq+8Aw11XstqxpSfR8_1NA@mail.gmail.com>
Date:	Thu, 13 Oct 2011 09:22:13 +0200
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	"Linux/m68k" <linux-m68k@...r.kernel.org>,
	linux-kernel@...r.kernel.org,
	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Linux-Next <linux-next@...r.kernel.org>
Subject: linux-m68k.git is back

Hi all,

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),
  - for-linus: What I will ask Linus to pull in this merge window,
  - for-next: What's destined for the next merge window,
  - for-*: What's destined for a specific merge window. The latest overlap with
    for-linus/for-next,
  - m68k-v*: State of m68k-queue when v* was current.

master and m68k-v* are never rebased. m68k-queue and for-* are rebased when a
new v* comes out.

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/