From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Sebastien Vauban <sva-news@mygooglest.com>,
Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Setting the value of `emacs-bzr-version' also from a git checkout
Date: Tue, 1 Oct 2013 22:23:58 +0200 [thread overview]
Message-ID: <CAH8Pv0iLFiCm9K3Pi14aL9j0rYEuiWR8u4Qy=nFTuPLW0g9=xA@mail.gmail.com> (raw)
>> It would be nice if I could specify the bzr revno manually, for
>> example as a parameter to "configure" or "make", because having to
>> keep using bzr just for this little thing would also be too bad.
>
> You need to set the value of emacs-bzr-version (a string) during
> dumping.
I see. As a temporary solution, I guess I could set that value
hard-coded, like this:
--------------------------------
diff --git a/lisp/loadup.el b/lisp/loadup.el
index c32bd00..5c1daab 100644
--- a/lisp/loadup.el
+++ b/lisp/loadup.el
@@ -299,8 +299,7 @@
(string-to-number
(substring name (length base) exelen))))
files)))
- (setq emacs-bzr-version (condition-case nil (emacs-bzr-get-version)
- (error nil)))
+ (setq emacs-bzr-version "rgm@gnu.org-20130925101746-8kz06nvtpjms0hy3")
;; `emacs-version' is a constant, so we shouldn't change it with `setq'.
(defconst emacs-version
(format "%s.%d"
--------------------------------
But I hope that `emacs-bzr-get-version' could be adapted to try a
second method when the primary one (the current one) fails.
That second method would assume a git repo instead of a bzr one
(Andreas showed how to get the bzr revid from a git repo).
--
Dani Moncayo
next reply other threads:[~2013-10-01 20:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 20:23 Dani Moncayo [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-01 16:45 Setting the value of `emacs-bzr-version' also from a git checkout (was: Emacs trunk binary on Dropbox) Dani Moncayo
2013-10-01 17:04 ` Setting the value of `emacs-bzr-version' also from a git checkout Óscar Fuentes
2013-10-01 17:45 ` Andreas Schwab
2013-10-01 18:37 ` Dani Moncayo
2013-10-01 18:46 ` Óscar Fuentes
2013-10-01 21:15 ` Dani Moncayo
2013-10-02 0:22 ` Stefan Monnier
2013-10-02 14:36 ` Josh
2013-10-12 10:22 ` Dani Moncayo
2013-10-12 10:33 ` Eli Zaretskii
2013-10-12 10:42 ` Dani Moncayo
2013-10-12 10:51 ` Óscar Fuentes
2013-10-12 10:58 ` Dani Moncayo
2013-10-12 11:16 ` Dani Moncayo
2013-10-12 11:40 ` Eli Zaretskii
2013-10-12 12:04 ` Dani Moncayo
2013-10-12 19:04 ` Óscar Fuentes
2013-10-12 20:36 ` Juanma Barranquero
2013-10-12 20:51 ` Óscar Fuentes
2013-10-12 20:57 ` Juanma Barranquero
2013-10-12 21:16 ` Óscar Fuentes
2013-10-12 21:33 ` Juanma Barranquero
2013-10-12 20:56 ` Stefan Monnier
2013-10-12 21:25 ` Dani Moncayo
2013-10-12 21:38 ` Óscar Fuentes
2013-10-12 10:58 ` Eli Zaretskii
2013-10-12 11:06 ` Dani Moncayo
2013-10-12 11:37 ` Eli Zaretskii
2013-10-13 20:49 ` Dani Moncayo
2013-10-13 22:16 ` Glenn Morris
2013-10-14 6:38 ` Dani Moncayo
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='CAH8Pv0iLFiCm9K3Pi14aL9j0rYEuiWR8u4Qy=nFTuPLW0g9=xA@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sva-news@mygooglest.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.
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).