From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ShengHuo ZHU <zsh@cs.rochester.edu>, ding@gnus.org
Subject: Re: emacs21-branch (Re: ognus)
Date: 29 Oct 2000 20:50:13 +0100 [thread overview]
Message-ID: <vaflmv78m16.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <20001029184843.3207BDBAC8@tux.gnu.franken.de>
On Sun, 29 Oct 2000, keichwa@gmx.net wrote:
> Okay, I see your point. The only solution I can see for the moment
> is to create another branch based on the `pre-ognus-point' tag.
> Right?
Sounds good to me. What should it be called? v_5_8? STABLE?
I'm proposing several tags:
* for each Gnus release, let there be a tag RELEASE_5_8_7 or similar,
which names a version (not a branch)
* for each Gnus version, let there be a tag V_5_8 or similar, which
names a branch and `slides' along as patches are added
* let there be a STABLE tag which is the current stable branch (ie, at
the moment it would be an alias for V_5_8, but when Oort Gnus has
come of age, it will be an alias for V_5_10)
* let there be a HEAD tag (need not be created, is implicitly there
anyway) which corresponds to the current development sources.
Thoughts?
Maybe we should put a chapter on the CVS organization into the manual.
kai
--
I like BOTH kinds of music.
next prev parent reply other threads:[~2000-10-29 19:50 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 22:59 ognus Simon Josefsson
2000-10-28 0:25 ` ognus ShengHuo ZHU
2000-10-28 13:41 ` ognus Simon Josefsson
2000-10-28 15:34 ` ognus Kai Großjohann
2000-10-28 15:41 ` ognus Simon Josefsson
2000-10-29 17:47 ` ognus Dave Love
2000-10-31 22:09 ` S/MIME and PGP/MIME (Was: Re: ognus) Bjørn Mork
2000-10-31 23:18 ` ShengHuo ZHU
2000-11-01 20:41 ` Bjørn Mork
2000-10-28 19:22 ` emacs21-branch (Re: ognus) Karl Eichwalder
2000-10-29 17:47 ` Dave Love
2000-10-29 18:48 ` Karl Eichwalder
2000-10-29 19:50 ` Kai Großjohann [this message]
2000-10-29 21:26 ` Florian Weimer
2000-10-29 22:53 ` ShengHuo ZHU
2000-10-30 22:53 ` Dave Love
2000-10-30 23:20 ` Denys Duchier
2000-10-30 23:38 ` Laura Conrad
2000-10-31 9:50 ` Denys Duchier
2000-11-02 17:25 ` Dave Love
2000-11-02 17:34 ` Gunnar Evermann
2000-11-03 19:09 ` Dave Love
2000-11-03 22:07 ` Gunnar Evermann
2000-11-02 21:01 ` Denys Duchier
2000-11-02 22:53 ` Kai Großjohann
2000-11-03 14:31 ` Per Abrahamsen
2000-11-03 14:42 ` luis fernandes
2000-11-04 11:42 ` Steinar Bang
2000-11-04 2:52 ` Russ Allbery
2000-11-03 19:14 ` Dave Love
2000-11-03 19:42 ` Denys Duchier
2000-11-04 0:04 ` Kai Großjohann
2000-11-04 15:04 ` Per Abrahamsen
2000-11-04 20:15 ` Denys Duchier
2000-11-04 22:59 ` Andreas Fuchs
2000-11-05 1:15 ` Russ Allbery
2000-11-02 17:23 ` Dave Love
2000-10-31 0:17 ` Steven E. Harris
2000-10-31 10:09 ` Kai Großjohann
2000-10-29 17:39 ` ognus Dave Love
2000-10-30 11:35 ` ognus Per Abrahamsen
2000-10-30 13:05 ` ognus Kai Großjohann
2000-10-30 23:24 ` ognus Dave Love
2000-10-31 10:16 ` ognus Kai Großjohann
2000-11-04 20:23 ` ognus Lars Magne Ingebrigtsen
2000-11-04 22:04 ` ognus Kai Großjohann
2000-11-04 22:34 ` ognus Lars Magne Ingebrigtsen
2000-10-30 23:22 ` ognus Dave Love
2000-10-31 9:07 ` ognus Russ Allbery
2000-10-31 13:06 ` ognus Karl Kleinpaste
2000-10-31 17:00 ` ognus Sean Doran
2000-10-31 17:55 ` ognus Kai Großjohann
2000-10-31 13:36 ` ognus Per Abrahamsen
2000-10-31 16:49 ` ognus Sean Doran
2000-11-02 17:35 ` ognus Dave Love
2000-11-02 18:08 ` ognus ShengHuo ZHU
2000-11-02 19:31 ` uunassigned code (was: Re: ognus) Per Abrahamsen
2000-11-03 19:01 ` ognus Dave Love
2000-11-02 19:18 ` ognus Per Abrahamsen
2000-11-02 23:01 ` ognus Kai Großjohann
2000-11-03 14:11 ` ognus Per Abrahamsen
2000-11-03 19:04 ` ognus Dave Love
2000-11-04 15:11 ` ognus Per Abrahamsen
2000-11-03 15:39 ` ognus Simon Josefsson
2000-11-04 20:31 ` ognus Lars Magne Ingebrigtsen
2000-10-31 16:37 ` ognus Sean Doran
2000-11-02 17:22 ` ognus Dave Love
2000-11-04 11:48 ` ognus Steinar Bang
2000-11-04 11:45 ` ognus Steinar Bang
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=vaflmv78m16.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
--cc=zsh@cs.rochester.edu \
/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).