Gnus development mailing list
 help / color / mirror / Atom feed
From: Romain Francoise <romain@orebokech.com>
Subject: Re: Version numbers of unreleased stable and development versions
Date: Thu, 13 Apr 2006 08:49:26 +0200	[thread overview]
Message-ID: <87r7427yx5.fsf@pacem.orebokech.com> (raw)
In-Reply-To: <m37j5vxvjv.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 12 Apr 2006 06:33:08 +0200")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Anyway, how about using an odd/even-numbered methodology?

I'd prefer that to the '+cvs' solution.

Or we could come up with two more code names for the CVS versions of the
stable and development releases and keep the same version numbers.  One
can never have enough code names.

-- 
Romain Francoise <romain@orebokech.com> | The sea! the sea! the open
it's a miracle -- http://orebokech.com/ | sea! The blue, the fresh, the
                                        | ever free! --Bryan W. Procter



  parent reply	other threads:[~2006-04-13  6:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-11 15:59 Reiner Steib
2006-04-11 18:14 ` Bill Wohler
2006-04-12  4:33   ` Lars Magne Ingebrigtsen
2006-04-12 22:54     ` Bill Wohler
2006-04-13  5:48       ` Lars Magne Ingebrigtsen
2006-04-13  6:49     ` Romain Francoise [this message]
2007-03-22 11:13 Inaccuracy in the documentation Tassilo Horn
2007-03-22 12:04 ` Katsumi Yamaoka
2007-03-23 18:17   ` Version numbers of unreleased stable and development versions (was: Inaccuracy in the documentation) Reiner Steib
2007-05-26  8:21     ` Version numbers of unreleased stable and development versions Reiner Steib
2007-05-28  9:03       ` Didier Verna
2007-05-28 12:57         ` Zlatko Calusic
2007-05-28 17:42         ` Reiner Steib
2007-05-29  7:21           ` Didier Verna
2007-05-31 19:01             ` Reiner Steib
2007-06-04  9:29               ` Didier Verna
2007-06-13 18:50                 ` Reiner Steib
2007-06-15 17:53                   ` Reiner Steib

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=87r7427yx5.fsf@pacem.orebokech.com \
    --to=romain@orebokech.com \
    /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).