From: Bernt Hansen <bernt@norang.ca>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Bastien Guerry <bzg@altern.org>,
Michael Brand <michael.ch.brand@gmail.com>,
Org Mode <emacs-orgmode@gnu.org>
Subject: Re: "git describe" in version of info file with "make info_git_describe"
Date: Sun, 23 Oct 2011 18:50:30 -0400 [thread overview]
Message-ID: <87sjmjz5jd.fsf@norang.ca> (raw)
In-Reply-To: <87r526l3v5.fsf@norang.ca> (Bernt Hansen's message of "Fri, 21 Oct 2011 12:13:34 -0400")
>> On Oct 16, 2011, at 9:12 PM, Michael Brand wrote:
>>
>>> I made a new patch replacing the previous, now considering the
>>> Makefile targets "target" and "help" introduced meanwhile by Achim
>>> Gratz and with a shorter name "info-vg" for the new target for easier
>>> typing of the make command.
>>>
>>> The previous patch attachment had a wrong mime type, could therefore
>>> not be caught by patchwork and has not been accepted.
>>>
>>> Michael
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> Hi,
>>
>> is there an agreement that this is a good patch? I have not followed the discussion.....
>>
>> - Carsten
>>
I'm fine with the actual text change for the version number so it
matches the git describe command. I'm not sure if all of the make
target changes make sense since I don't normally use those.
Regards,
Bernt
next prev parent reply other threads:[~2011-10-23 22:50 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 [this message]
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=87sjmjz5jd.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=bzg@altern.org \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=michael.ch.brand@gmail.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/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).