From: Tom Rini <trini@kernel.crashing.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: linux-2.4-mpc5xxx repository updates
Date: Wed, 21 Jan 2004 10:01:51 -0700 [thread overview]
Message-ID: <20040121170151.GS13454@stop.crashing.org> (raw)
I know it's been a while, and the general consensious (as I read it at
least) was that this code is still too ugly to get to kernel.org, but
regardless, I've finally gotten around to updating this repository
again. And this time I didn't restart the repository from scratch, I
just pushed. The only change is:
- From Dale Farnsworth, fix the IceCube support
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-01-21 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 17:01 Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-21 20:32 linux-2.4-mpc5xxx repository updates Wolfgang Denk
2004-01-21 21:46 ` Benjamin Herrenschmidt
2004-01-22 16:59 ` Tom Rini
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=20040121170151.GS13454@stop.crashing.org \
--to=trini@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).