From: Michael Brand <michael.ch.brand@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: "git describe" in version of info file with "make info_git_describe"
Date: Sun, 30 Oct 2011 15:20:10 +0100 [thread overview]
Message-ID: <CALn3zoiOAYEkqCpHq3G2kihjNSY98Zy7VSQCgZmyiE0gZAwK6A@mail.gmail.com> (raw)
In-Reply-To: <87ipn7m094.fsf@Rainer.invalid>
Hi Achim
On Sun, Oct 30, 2011 at 08:01, Achim Gratz <Stromeko@nexgo.de> wrote:
> 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.
Now I see. No need for that, I didn't take into account that git
describe is not used to _replace_ "7.7" any more as my simpler
implementation did but is just _added_. Again the cleaner solution,
without the need for different behaviors.
Michael
prev parent reply other threads:[~2011-10-30 14:20 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
2011-10-30 14:20 ` Michael Brand [this message]
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=CALn3zoiOAYEkqCpHq3G2kihjNSY98Zy7VSQCgZmyiE0gZAwK6A@mail.gmail.com \
--to=michael.ch.brand@gmail.com \
--cc=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).