From: Russell King <rmk@arm.linux.org.uk>
To: Dominik Brodowski <linux@brodo.de>
Cc: Jan Rychter <jan@rychter.com>, Ducrot Bruno <ducrot@poupinou.org>,
cpufreq@www.linux.org.uk
Subject: Re: cpufreq CVS [Was: Re: cpufreq and P-IIIM]
Date: Mon, 18 Aug 2003 19:33:49 +0100 [thread overview]
Message-ID: <20030818193349.F1737@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030818182137.GA2296@brodo.de>; from linux@brodo.de on Mon, Aug 18, 2003 at 08:21:37PM +0200
On Mon, Aug 18, 2003 at 08:21:37PM +0200, Dominik Brodowski wrote:
> Also, it is my impression that an external CVS tree is used far less if a
> feature is merged into a mainline kernel. If it's not in the kernel, keeping
> track of a project without something like CVS is impossible. So I'm really
> glad about having had cpufreq-CVS and FTP-archives available. But, for the
> future, I don't see such a strong reason for keeping it.
As you're aware (we discussed this at the time when cpufreq was merged
into 2.5) that's my POV as well.
That just leaves davej and ducrot to say exactly what they want killed.
I'll consider going as far as taring up the CVS tree as it currently
stands and putting that on the ftp site for history, if that's what
people want.
But people have to tell me... 8)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-08-18 18:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 20:28 cpufreq and P-IIIM Jan Rychter
2003-08-18 11:29 ` Ducrot Bruno
2003-08-18 17:02 ` Jan Rychter
2003-08-18 18:07 ` Russell King
2003-08-18 18:21 ` cpufreq CVS [Was: Re: cpufreq and P-IIIM] Dominik Brodowski
2003-08-18 18:33 ` Russell King [this message]
2003-08-20 11:25 ` Ducrot Bruno
2003-08-20 17:30 ` Benjamin Herrenschmidt
2003-08-19 14:57 ` Bas Mevissen
2003-08-18 17:18 ` cpufreq and P-IIIM Jan Rychter
2003-08-19 8:03 ` Ducrot Bruno
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=20030818193349.F1737@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.org \
--cc=jan@rychter.com \
--cc=linux@brodo.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.