From: Greg Ungerer <gerg@snapgear.com>
To: linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: m68knommu git tree is back on kernel.org
Date: Fri, 11 Nov 2011 15:55:53 +1000 [thread overview]
Message-ID: <4EBCB8E9.9030704@snapgear.com> (raw)
Hi All,
The m68knommu git tree is now back on git.kernel.org.
You can get at it in the same location as the old kernel.org:
http://git.kernel.org/?p=linux/kernel/git/gerg/m68knommu.git;a=summary
The current interesting branches:
for-linus -- what I will ask Linux to pull in the next merge window
for-next -- what is being pulled into linux-next
cfmmu -- work-in-progressto support MMU on ColdFire
I won't be updating the m68knommu git tree on github any longer. And
in the very near future I will ask Stephen Rothwell to pull the
m68knommu for-next branch from kernel.org instead of github.
Regards
Greg
--
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
reply other threads:[~2011-11-11 5:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EBCB8E9.9030704@snapgear.com \
--to=gerg@snapgear.com \
--cc=linux-m68k@lists.linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox