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: Sun, 30 Oct 2011 08:01:11 +0100 [thread overview]
Message-ID: <87ipn7m094.fsf@Rainer.invalid> (raw)
In-Reply-To: CALn3zojd61JJ+b1EkxnDG1gDx024Gui--E5ZjHzDsQU_TqQ7mw@mail.gmail.com
Michael Brand <michael.ch.brand@gmail.com> writes:
> Is it possible with your current "make info" to get an info file
> without git describe for a release like ELPA when made from within a
> git repo
Why should the git-describe info not be part of the ELPA tarball? If
there is a good reason not to include it (I think it is useful
to know which commit the ELPA archive was built on) one could alter the
include file before rolling the tar ball of course.
> and also for Emacs when building Emacs from a bzr-mirroring
> git repo?
Emacs does have its own build system. So there's be two possibilities:
a) just copy over git-decribe.texi as is or b) alter it and put in any
information that's deemed more appropriate before it gets copied over to
bzr. It might even be useful to actually include the information back
into the org.texi file to have a single file. Once it is decided how
this should be handled, it can all become part of the makefile of
course.
Please note that the name "git-describe.texi" is only a suggestion and
should probably be changed later on to something like "version.texi".
>> Anyway, I've implemented the requested functionality into my Makefile
>> fork, please test.
>
> Thank you for this implementation. Since my patch discussed here is
> now superseded by your branch I thought it would be cleaner to put my
> comments to the sub-thread "Makefile restructuring" starting here:
> http://lists.gnu.org/archive/html/emacs-orgmode/2011-07/msg00680.html
Thank you.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2011-10-30 7:01 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
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 [this message]
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=87ipn7m094.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).