From: "Chuck Meade" <chuckmeade@mindspring.com>
To: <linuxppc-dev@lists.linuxppc.org>
Subject: official patches ceasing at 2.4.18 on kernel.org?
Date: Wed, 2 Jul 2003 22:26:45 -0400 [thread overview]
Message-ID: <IIEEICKJLNEPBBDJICNGAEBGDIAA.chuckmeade@mindspring.com> (raw)
Is there a reason that the ppc patches directory under the
kernel.org ports area has not been updated with patches since
2.4.18?
I saw that Geert was offering to create one for 2.4.21, and that
would be great -- just wondering why placing patches out there
on kernel.org has ceased.
I am creating a local ppc 2.4.21 tree. I see the following are
the most recent 2.4.21 tags on the BK server:
v2.4.21_linuxppc_2_4_devel
v2.4.21_linuxppc
v2.4.21
What is the significance of these three different tags?
What does each represent?
What would be great is for the patches under ports on kernel.org
to be carried forward/kept up to date. If that is not going to
be continued, then what is the best way to create the same thing,
i.e. a solid 2.4.21 ppc tree, using what is available via BK?
Thanks,
Chuck
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-07-03 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 2:26 Chuck Meade [this message]
2003-07-03 16:44 ` official patches ceasing at 2.4.18 on kernel.org? Tom Rini
2003-07-03 16:51 ` Chuck Meade
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=IIEEICKJLNEPBBDJICNGAEBGDIAA.chuckmeade@mindspring.com \
--to=chuckmeade@mindspring.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).