Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: Oort Gnus branch
Date: 01 Oct 2000 23:25:36 +1100	[thread overview]
Message-ID: <87aecokatb.fsf@inanna.danann.net> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "01 Oct 2000 14:11:15 +0200"

On 01 Oct 2000, Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
wrote:

> On Sun, 1 Oct 2000, ShengHuo ZHU wrote:
> 
>> I think it will be a new branch.
> 
> 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 would have to second this. Personal experience with CVS suggests that
you do a far, far better thing putting the newest development on head.

[...]

> Another thought is that maybe we would like to do it like Emacs does
> it.  So, how does Emacs handle the branches?

I don't know about Emacs, but XEmacs was doing trunk development on a
branch, but plan on moving it to the head branch.

        Daniel

-- 
We close our eyes and look in opposite direction.
We ignore the threats and hope they'll go away.
We refuse to pay attention to the dangers we create
in the name of our fathers we kill our children.
        -- Covenant, _Theremin_



  reply	other threads:[~2000-10-01 12:25 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 [this message]
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
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=87aecokatb.fsf@inanna.danann.net \
    --to=daniel@rimspace.net \
    /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).