From: benh@kernel.crashing.org
To: <acurtis@onz.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: linuxppc_2_5 vs. linuxppc-2.5
Date: Mon, 13 May 2002 16:50:33 +0100 [thread overview]
Message-ID: <20020513155033.14447@mailhost.mipsys.com> (raw)
In-Reply-To: <NCBBIINEHIPFGJPLBEIFCEPBDGAA.acurtis@onz.com>
>Is one of these BitKeeper trees now obsolete? The webpage on
>www.penguinppc.org has been partially updated to specify linuxppc-2.5.
>(originally linuxppc_2_5)
The _2_5 is obsolete, we keep it around for the history
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-05-13 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 14:09 linuxppc_2_5 vs. linuxppc-2.5 Allen Curtis
2002-05-13 15:50 ` benh [this message]
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=20020513155033.14447@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=acurtis@onz.com \
--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).