From: Bastien <bzg@gnu.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-devel@gnu.org
Subject: Re: Reminder about feature freeze on Oct 1
Date: Sun, 30 Sep 2012 12:00:30 +0200 [thread overview]
Message-ID: <87y5jrrfsx.fsf@bzg.ath.cx> (raw)
In-Reply-To: <871uhjyhsw.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 30 Sep 2012 11:35:27 +0200")
Hi Achim,
Achim Gratz <Stromeko@nexgo.de> writes:
> Both the patch you sent to the list and the patch you uploaded to your
> site doesn't seem to include a file org-version.el.
I used bzr diff but I guess it does include files that are not
known to bzr, that's surely why.
> As to the difference: a bog-standard org-version.el would record a git
> version that doesn't make any sense in Emacs bzr, so the invocation I
> gave replaces that part with "GNU-Emacs". That will also help in
> figuring out which version people talk about in bug reports.
That makes sense.
> If you'd
> like to keep the Git commit we could do the same as we do for the ELPA
> archives and just strip "release_" and then add "-GNU-Emacs", but that
> requires support from the Makefile.
I don't want to keep the Git commit.
Thanks!
--
Bastien
prev parent reply other threads:[~2012-09-30 10:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABfhpz6ov=dqSddKpNFNs7DOXojB1rRu0rtFnDHzsWJ2yhvtJQ@mail.gmail.com>
2012-09-29 13:47 ` Reminder about feature freeze on Oct 1 Chong Yidong
2012-09-29 15:01 ` Bastien
2012-09-30 7:35 ` Bastien
2012-09-30 15:38 ` Bastien
2012-09-30 16:03 ` Eli Zaretskii
2012-09-30 16:30 ` Achim Gratz
2012-09-30 16:52 ` Bastien
2012-09-30 17:59 ` Eli Zaretskii
2012-09-30 18:21 ` Bastien
2012-09-30 19:08 ` Glenn Morris
2012-09-30 21:12 ` Bastien
2012-09-30 7:42 ` Bastien
2012-09-30 8:00 ` Eli Zaretskii
2012-09-30 8:03 ` Bastien
2012-09-30 8:54 ` Achim Gratz
2012-09-30 8:57 ` Bastien
2012-09-30 9:35 ` Achim Gratz
2012-09-30 10:00 ` Bastien [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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y5jrrfsx.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=Stromeko@nexgo.de \
--cc=emacs-devel@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.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).