Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Grant Grundler <grundler@puffin.external.hp.com>
Cc: Paul Bame <bame@fc.hp.com>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] 2.5 kernel and CVS -- opinions?
Date: Wed, 12 Dec 2001 23:35:05 +0100	[thread overview]
Message-ID: <20011212233505.C1998@solo.franken.de> (raw)
In-Reply-To: <200112120429.VAA03750@puffin.external.hp.com>; from grundler@puffin.external.hp.com on Tue, Dec 11, 2001 at 09:29:25PM -0700

On Tue, Dec 11, 2001 at 09:29:25PM -0700, Grant Grundler wrote:
> Paul Bame wrote:
> > It's time to start tracking the 2.5 kernel at cvs.parisc-linux.org
> > and there are a few different ways to do it -- I'm looking for opinions.
> > My favorite option at the moment is 1A.
> 
> I'm ok with 1A as well:

I don't have a hard opinion whether having two tree makes more sense than
trunk/branch hoping. People will probably work for some time on 2.4
and switch over to 2.5, so I guess two trees are ok.

> o *someday*, I hope the CVS date-based check out will get fixed.
> o TAGs work and I'm ok with tag being used.

tags are sometimes nice, but too much tags aren't. Try a cvs log with hundreds
of tags. That's not funny. And btw. tags are (re-)movable and they don't have a
history, which makes them pretty useless for any serious build system. At
work we use seperate cvs controlled sourcelists, which lists every file with
its revision of a release. That way it's always possible to rebuild an old
release even if a dork moved/removed a tag.

> o We could TAG weekly (or monthly) and keep enough nightly
>   checkout's to cover two or three tags. Or whatever we can
>   afford for diskspace.

I don't see a point for needing that. But maybe I'm just overlooking something.

I personaly wouldn't touch 2.5 at the moment. Right now 2.5 looks to
me like an adventure park of out of control kids. That's ok but IMHO it
doesn't help Linux/PARISC development. Hunting generic bugs mixed with
architecture bugs isn't fun. Let's wait until 2.5 settles and Linus will
accept PARISC inclusion (which he won't at the moment).

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea.                                 [ Alexander Viro on linux-kernel ]

      reply	other threads:[~2001-12-12 22:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11 16:44 [parisc-linux] 2.5 kernel and CVS -- opinions? Paul Bame
2001-12-12  4:29 ` Grant Grundler
2001-12-12 22:35   ` Thomas Bogendoerfer [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=20011212233505.C1998@solo.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=bame@fc.hp.com \
    --cc=grundler@puffin.external.hp.com \
    --cc=parisc-linux@parisc-linux.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