From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: "git describe" in version of info file with "make info_git_describe"
Date: Wed, 26 Oct 2011 18:56:47 +0200 [thread overview]
Message-ID: <87fwifwv1s.fsf@Rainer.invalid> (raw)
In-Reply-To: CALn3zogQ0NB-WoNuQZaPjJyBvvkJE_pr-dcjhX5KJUtGxQV=Aw@mail.gmail.com
Michael Brand <michael.ch.brand@gmail.com> writes:
> There has not yet been any review or comment on the changes in the
> Makefile and in UTILITIES/set-version.pl. I would be happy if these
> parts could be reviewed too.
The set-version.pl file may be obsolete (perl is still required), there
is no version number in the individual lisp files anymore. For
installation I've already added a replacement of the version cookie in
org.el with git-describe in my own fork of org-mode ([1] - I don't know if
you've checked it). It would be easy to do the same for org-texi,
albeit before compilation, not only during install. I
I agree it would be useful to have the full version recorded in the
resulting manual, but you really cannot alter the source file (git
status would always be dirty or the version would be wrong, wouldn't it?
:-).
[1] http://permalink.gmane.org/gmane.emacs.orgmode/44567
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2011-10-26 16:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 14:11 "git describe" in version of info file with "make info_git_describe" Michael Brand
2011-06-02 14:47 ` Bernt Hansen
2011-06-02 15:05 ` Michael Brand
2011-06-02 19:36 ` Michael Brand
2011-10-16 19:12 ` Michael Brand
2011-10-21 14:44 ` Carsten Dominik
2011-10-21 16:13 ` Bernt Hansen
2011-10-23 22:50 ` Bernt Hansen
2011-10-26 16:07 ` Michael Brand
2011-10-26 16:56 ` Achim Gratz [this message]
2011-10-27 18:24 ` Michael Brand
2011-10-28 9:26 ` Achim Gratz
2011-10-29 11:40 ` Michael Brand
2011-10-30 7:01 ` Achim Gratz
2011-10-30 14:20 ` Michael Brand
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fwifwv1s.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.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/org-mode.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).