From: Miles Bader <miles@lsi.nec.co.jp>
Cc: snogglethorpe@gmail.com, emacs-devel@gnu.org, rms@gnu.org,
"Jérôme Marant" <jmarant@free.fr>, "Kim F. Storm" <storm@cua.dk>
Subject: Re: Updating release version to 22.1
Date: Wed, 09 Feb 2005 19:52:37 +0900 [thread overview]
Message-ID: <buois52c8ei.fsf@mctpc71.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <x53bw6dnai.fsf@lola.goethe.zz> (David Kastrup's message of "Wed, 09 Feb 2005 11:45:41 +0100")
David Kastrup <dak@gnu.org> writes:
> This assumes that most version numbers in the text can stay ("will be
> available with version xxx" is a good candidate). That will still
> need to cater for "the current version is xxx", but maybe _those_ can
> partly be autogenerated with CVS keywords, depending on the kind of
> text?
Certainly it would be better to use a variable than straight text where
possible. But, please, no !@#$ cvs keywords (which have bugger-all
connection to anything real anyway).
Where do all these instances of release numbers occur anyway? (Kim?)
Cases in lisp code obviously should refer to a lisp variable instead
(emacs-version, emacs-next-major-release :-).
Cases in help text or texinfo could possibly be addressed with some
analogous mechanism.
-Miles
--
"1971 pickup truck; will trade for guns"
next prev parent reply other threads:[~2005-02-09 10:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 13:06 Updating release version to 22.1 Kim F. Storm
2005-02-08 13:34 ` David Kastrup
2005-02-08 14:46 ` Stefan Monnier
2005-02-08 15:05 ` Kim F. Storm
2005-02-08 15:43 ` Han Boetes
2005-02-08 16:24 ` David Kastrup
2005-02-08 15:58 ` David Kastrup
2005-02-08 20:12 ` Kim F. Storm
2005-02-08 21:18 ` Jérôme Marant
2005-02-08 22:34 ` David Kastrup
2005-02-08 22:38 ` Miles Bader
2005-02-09 0:17 ` Kim F. Storm
2005-02-09 0:32 ` David Kastrup
2005-02-09 1:21 ` Miles Bader
2005-02-09 8:30 ` Kim F. Storm
2005-02-09 8:41 ` Miles Bader
2005-02-09 11:23 ` Kim F. Storm
2005-02-09 13:32 ` Robert J. Chassell
2005-02-09 13:59 ` David Kastrup
2005-02-09 14:15 ` Jason Rumney
2005-02-10 18:39 ` Richard Stallman
2005-02-10 21:49 ` Kim F. Storm
2005-02-10 22:33 ` Jérôme Marant
2005-02-10 22:52 ` David Kastrup
2005-02-09 14:21 ` Lennart Borgman
2005-02-09 14:56 ` Kim F. Storm
2005-02-09 9:44 ` Lute Kamstra
2005-02-09 10:54 ` Kim F. Storm
2005-02-09 10:45 ` David Kastrup
2005-02-09 10:52 ` Miles Bader [this message]
2005-02-09 11:33 ` Kim F. Storm
2005-02-10 6:01 ` Richard Stallman
2005-02-09 16:08 ` DONE: " Kim F. Storm
2005-02-09 16:32 ` David Kastrup
2005-02-09 17:39 ` Rob Browning
2005-02-10 6:01 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=buois52c8ei.fsf@mctpc71.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=emacs-devel@gnu.org \
--cc=jmarant@free.fr \
--cc=miles@gnu.org \
--cc=rms@gnu.org \
--cc=snogglethorpe@gmail.com \
--cc=storm@cua.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).