emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Brand <michael.ch.brand@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: "git describe" in version of info file with "make info_git_describe"
Date: Thu, 2 Jun 2011 17:05:42 +0200	[thread overview]
Message-ID: <BANLkTi=QfRwsDJjBWzcyuEsi91Zdu3Pseg@mail.gmail.com> (raw)
In-Reply-To: <87fwnse1d8.fsf@norang.ca>

On Thu, Jun 2, 2011 at 16:47, Bernt Hansen <bernt@norang.ca> wrote:
> Michael Brand <michael.ch.brand@gmail.com> writes:
>> Can I remove this substitution of "release_7.5-350-g3433" ->
>> "release_7.5.350.g3433" from org-version in my patch or should "make
>> info_git_describe" do the same and why?
>
> Hi Michael,
>
> This was purely cosmetic.  I didn't like the look of the mixed '.' and
> '-' in the version number originally.

... and '_' ... :-)

> I think the two reported version
> numbers should be consistent between the org-version function and the
> documentation version function you are proposing.
>
> If you want to remove the substitution please also do so in the
> org-version code so the reported numbers are consistent.

Since I would like to give the more often used "git describe"
precedence I will make org-version and "make info_git_describe"
consistent with git. The ".dirty" postfix of org-version I will leave
untouched in org-version of course and support also in "make
info_git_describe".

Michael

  reply	other threads:[~2011-06-02 15:09 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 [this message]
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

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='BANLkTi=QfRwsDJjBWzcyuEsi91Zdu3Pseg@mail.gmail.com' \
    --to=michael.ch.brand@gmail.com \
    --cc=bernt@norang.ca \
    --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).