From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: raeburn@raeburn.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Canonical location for emacs-version string in source tree?
Date: Sat, 22 May 2010 12:03:06 -0400 [thread overview]
Message-ID: <E1OFrAI-0006vD-V1@fencepost.gnu.org> (raw)
In-Reply-To: <83ocg9ym77.fsf@gnu.org> (message from Eli Zaretskii on Sat, 22 May 2010 00:33:16 +0300)
> A simple fix is to get rid of the DOC-NN.NN.NN madness and just use
> "DOC" as the file name. Any objection?
Would the emacs-NN.NN.NN madness go with it as well?
Using version numbers in the DOC file name (and elsewhere) makes it
possible for multiple Emacs versions to coexist. And putting the version
numbers in the executables is useful for this too. You can install
the executable under whatever name you like.
next prev parent reply other threads:[~2010-05-22 16:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 16:57 Canonical location for emacs-version string in source tree? Jeff Kowalczyk
2010-05-20 17:12 ` Ken Raeburn
2010-05-20 18:01 ` Eli Zaretskii
2010-05-21 1:39 ` Ken Raeburn
2010-05-21 5:44 ` Eli Zaretskii
2010-05-21 20:19 ` Stefan Monnier
2010-05-21 21:33 ` Eli Zaretskii
2010-05-22 0:54 ` Stefan Monnier
2010-05-22 2:24 ` Ken Raeburn
2010-05-22 13:07 ` Stefan Monnier
2010-05-22 6:32 ` Eli Zaretskii
2010-05-22 16:03 ` Richard Stallman [this message]
2010-05-23 13:19 ` Stefan Monnier
2010-05-23 13:44 ` Lennart Borgman
2010-05-23 14:16 ` Drew Adams
2010-05-24 13:14 ` Stefan Monnier
2010-05-24 13:57 ` Drew Adams
2010-05-24 14:13 ` Stefan Monnier
2010-05-24 14:25 ` Drew Adams
2010-05-24 13:58 ` Ken Raeburn
2010-05-24 14:16 ` Stefan Monnier
2010-05-24 14:50 ` Ken Raeburn
2010-05-24 14:21 ` Drew Adams
2010-05-24 15:38 ` Richard Stallman
2010-05-24 17:44 ` Stefan Monnier
2010-05-21 5:44 ` Ulrich Mueller
2010-05-20 19:57 ` Stefan Monnier
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=E1OFrAI-0006vD-V1@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=raeburn@raeburn.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.
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).