All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@brodo.de>
To: Jan Rychter <jan@rychter.com>, Ducrot Bruno <ducrot@poupinou.org>,
	cpufreq@www.linux.org.uk
Subject: cpufreq CVS [Was: Re: cpufreq and P-IIIM]
Date: Mon, 18 Aug 2003 20:21:37 +0200	[thread overview]
Message-ID: <20030818182137.GA2296@brodo.de> (raw)
In-Reply-To: <20030818190710.C1737@flint.arm.linux.org.uk>

On Mon, Aug 18, 2003 at 07:07:10PM +0100, Russell King wrote:
> On Mon, Aug 18, 2003 at 10:02:29AM -0700, Jan Rychter wrote:
> >  Ducrot> That version is way too old anyway.
> > 
> > Huh? That was the latest 2.4 snapshot that I was able to pull from
> > ftp.linux.org.uk: cpufreq-LINUX_2_4-20030816.tar.bz2.
> > 
> > If these are not the 'official' archives and the snapshots are outdated,
> > I'd humbly suggest pulling them off the net, because it confuses
> > people.
> 
> As far as I'm concerned (as being the guy running the CVS and FTP
> archive) they remain official until the cpufreq maintainers explicitly
> tell me otherwise.
> 
> Maintainers need to either check their changes into the CVS tree or
> tell me that they no longer wish to use CVS, or tell me that they
> want a 2.4-ac branch, or whatever.

AFAICS, 
a) the 2.6. branch development is done in Dave's BK tree. 
b) 2.4-new [== backport of 2.6. to 2.4.] was never done in CVS,
c) 2.4-ac tags exist, but because of b) are not kept up to date,
d) depending on the outcome of the ARM and cpufreq-2.4. issue,
   2.4-stable [which is CVS LINUX_2_4] is going to be deprecated soon.

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.

Just my ¤0.02
	Dominik

  reply	other threads:[~2003-08-18 18:21 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       ` Dominik Brodowski [this message]
2003-08-18 18:33         ` cpufreq CVS [Was: Re: cpufreq and P-IIIM] Russell King
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=20030818182137.GA2296@brodo.de \
    --to=linux@brodo.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=ducrot@poupinou.org \
    --cc=jan@rychter.com \
    /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.