Gnus development mailing list
 help / color / mirror / Atom feed
From: Bruce Stephens <bruce+gnus@cenderis.demon.co.uk>
Subject: Re: Oort Gnus branch
Date: 01 Oct 2000 13:48:50 +0100	[thread overview]
Message-ID: <87vgvcohfx.fsf@cenderis.demon.co.uk> (raw)
In-Reply-To: <vafsnqgoj6k.fsf@lucy.cs.uni-dortmund.de>

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

[...]

> IMHO, it would be better if the main trunk was always the most current
> development version.  This way, people who use CVS get to test the
> most current version -- that's what CVS is here for, right?  Also, I
> think we expect the 5.8/5.9 lines of development to be rather short,
> no?
> 
> I think this is the first time that a major release is begun while
> using CVS, isn't it?  If it wasn't the first time, we could have
> looked at how it was done previously.
> 
> Another thought is that maybe we would like to do it like Emacs does
> it.  So, how does Emacs handle the branches?

Don't know about Emacs, but XEmacs does it the wrong way around: the
new development is on a branch (release-21-2).  (There's a comment on
the web page somewhere that they plan to change this.)

Your initial paragraph describes it as it should be, IMHO: cut a
branch to support bug fixes and things for pgnus, and ognus should be
on the head.



  parent reply	other threads:[~2000-10-01 12:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-30 23:41 ShengHuo ZHU
2000-10-01  6:14 ` Norbert Koch
2000-10-01 11:45   ` ShengHuo ZHU
2000-10-01 12:11     ` Kai Großjohann
2000-10-01 12:25       ` Daniel Pittman
2000-10-01 12:34         ` Norbert Koch
2000-10-01 13:20         ` ShengHuo ZHU
2000-10-01 13:56           ` William M. Perry
2000-10-03 22:47             ` Dave Love
2000-10-01 12:48       ` Bruce Stephens [this message]
2000-10-01 12:19     ` Karl Eichwalder
2000-10-01 16:49 ` Florian Weimer
2000-10-01 16:44 Sean Doran
2000-10-01 18:59 ` Kai Großjohann
2000-10-01 21:41 ` Russ Allbery

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=87vgvcohfx.fsf@cenderis.demon.co.uk \
    --to=bruce+gnus@cenderis.demon.co.uk \
    /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).