From: Norbert Koch <nk@LF.net>
Cc: ding@gnus.org
Subject: Re: Oort Gnus branch
Date: 01 Oct 2000 14:34:00 +0200 [thread overview]
Message-ID: <vzlmw8viyv.fsf@lamia.LF.net> (raw)
In-Reply-To: <87aecokatb.fsf@inanna.danann.net>
Daniel Pittman <daniel@rimspace.net> wrote:
Hi!
> 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.
I absolutely agree to this.
> I don't know about Emacs, but XEmacs was doing trunk development on a
> branch, but plan on moving it to the head branch.
As usual it lacks time ;-/
norbert.
next prev parent reply other threads:[~2000-10-01 12:34 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 [this message]
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=vzlmw8viyv.fsf@lamia.LF.net \
--to=nk@lf.net \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).