From: David Gibson <david@gibson.dropbear.id.au>
To: linuxppc-dev <Linuxppc-dev@ozlabs.org>, linuxppc64-dev@ozlabs.org
Subject: dtc git tree has moved (and maintainership announcement)
Date: Thu, 16 Mar 2006 11:58:35 +1100 [thread overview]
Message-ID: <20060316005835.GB1512@localhost.localdomain> (raw)
For the next six months or so, I will be available intermittently at
best for dtc work. For this reason, Jon Loeliger of Freescale has
agreed to take over dtc maintainership for the interim.
As part of the logistics of this handover, the location of the dtc git
tree has changed. It is now available *only* via git daemon (not http
or rsync, sorry), the address is:
git://ozlabs.org/srv/projects/dtc/dtc.git
There is also now a web page for dtc, although at present there's
basically no information there, at:
http://dtc.ozlabs.org/
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
reply other threads:[~2006-03-16 0:58 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=20060316005835.GB1512@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=Linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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