From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: Installing the Emacs executable
Date: Fri, 19 Apr 2013 21:49:28 +0300 [thread overview]
Message-ID: <83k3ny1hl3.fsf@gnu.org> (raw)
In-Reply-To: <m2ppxqml0e.fsf@igel.home>
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> Date: Fri, 19 Apr 2013 20:29:53 +0200
>
> Glenn Morris <rgm@gnu.org> writes:
>
> > Andreas Schwab wrote:
> >
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >>
> >>> Is this done on purpose? Why isn't the binary named the same as its
> >>> DOC, i.e. emacs-24.3.50.nn?
> >>
> >> I'd rather see the build number removed at all.
> >
> > I agree with you (IIUC what you are saying); I've never found it useful.
> > (IIRC rms is/was a fan of it.)
>
> Like this:
>
> * loadup.el: Don't append build number to emacs-version.
This will overwrite the previous Emacs binary in src as well (and its
DOC in etc), won't it? Do we really want to toss the possibility of
being able to easily run previous builds of the same version?
next prev parent reply other threads:[~2013-04-19 18:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 16:32 Installing the Emacs executable Eli Zaretskii
2013-04-16 17:15 ` Andreas Schwab
2013-04-16 17:20 ` Glenn Morris
2013-04-16 18:11 ` Eli Zaretskii
2013-04-19 18:29 ` Andreas Schwab
2013-04-19 18:49 ` Eli Zaretskii [this message]
2013-04-19 18:57 ` Glenn Morris
2013-04-19 19:05 ` Eli Zaretskii
2013-04-19 19:08 ` Glenn Morris
2013-04-20 1:48 ` Stefan Monnier
2013-04-19 20:58 ` Andreas Schwab
2013-04-20 6:37 ` Eli Zaretskii
2013-04-20 10:44 ` Andreas Schwab
2013-04-20 10:56 ` Eli Zaretskii
2013-04-20 11:55 ` Andreas Schwab
2013-04-20 12:31 ` Eli Zaretskii
2013-04-20 13:24 ` Andreas Schwab
2013-04-20 15:43 ` Eli Zaretskii
2013-04-20 15:56 ` Andreas Schwab
2013-04-24 5:05 ` Ken Raeburn
2013-04-24 13:12 ` Stefan Monnier
2013-04-24 17:06 ` Eli Zaretskii
2013-04-24 18:54 ` 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=83k3ny1hl3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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).