Gnus development mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
Subject: Re: Modeline oddness in 0.97
Date: 27 Sep 1999 16:33:01 -0300	[thread overview]
Message-ID: <or905si1zm.fsf@cupuacu.lsd.ic.unicamp.br> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "27 Sep 1999 21:07:33 +0200"

On Sep 27, 1999, Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:

> Mike Fletcher <mfletcher@iss.net> writes:
>> Maybe the day of the year (i.e. (time-to-day-in-year (current-time))), 
>> or the week of the year if they're going to be less frequent?  Or the
>> more verbose but less ambiguous v0.97.YYYYMMDD?

> That would make the continuum-version kinda large:

> (gnus-continuum-version "Pterodactyl Gnus v0.97.1")
> => 5.07009701

> (gnus-continuum-version "Pterodactyl Gnus v0.97.19990927")
> => 5.07009719990927

> But, like, why not?

It's been common practice (at least in some projects I work on) to add
letters to version strings to indicate unreleased version, or even
``odd'' letters for CVS versions and ``even'' letters for ``released''
test versions/snapshots.

Another interesting option, that the libtool team has adopted, is to
append to the regular version number the ChangeLog revision number and
its CVS timestamp.  One advantage of this scheme is that it will
unambiguously identify branches and arbitrary check-outs, and you
won't have to bother about making commits at regular intervals just to
change the version number.  There's a script (`mkstamp') in the
libtool CVS tree and recent distributions that will extract the
version number from the ChangeLog.  libtool runs this script off
`configure'

-- 
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoliva@{acm,computer}.org
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them



  reply	other threads:[~1999-09-27 19:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-27 15:19 Pterodactyl Gnus v0.97 is released Lars Magne Ingebrigtsen
1999-09-27 16:41 ` Modeline oddness in 0.97 Paul Stevenson
1999-09-27 16:47   ` Lars Magne Ingebrigtsen
1999-09-27 18:17     ` David S. Goldberg
1999-09-27 18:24       ` Mike Fletcher
1999-09-27 18:40         ` Lars Magne Ingebrigtsen
1999-09-27 18:52           ` Mike Fletcher
1999-09-27 19:07             ` Lars Magne Ingebrigtsen
1999-09-27 19:33               ` Alexandre Oliva [this message]
1999-09-28  8:21           ` Steinar Bang
1999-09-30  0:36             ` Raja R Harinath
1999-09-27 18:30       ` Lars Magne Ingebrigtsen
1999-09-27 18:37         ` Paul Stevenson
1999-09-27 16:53   ` Karl Kleinpaste
1999-09-27 16:57 ` Pterodactyl Gnus v0.97 is released Stainless Steel Rat

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=or905si1zm.fsf@cupuacu.lsd.ic.unicamp.br \
    --to=oliva@lsd.ic.unicamp.br \
    /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).