From: Glenn Morris <rgm@gnu.org>
To: Bastien Guerry <bzg@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: /srv/bzr/emacs/trunk r110286: Sync Org 7.9.2 from the commit tagged "release_7.9.2" in Org's Git repo.
Date: Sun, 30 Sep 2012 20:26:58 -0400 [thread overview]
Message-ID: <mn391z6nql.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E1TILGf-0007Kr-Mg@vcs.savannah.gnu.org> (Bastien Guerry's message of "Sun, 30 Sep 2012 17:14:59 +0200")
Only trivial comments:
ChangeLog entries that are not applicable (as already mentioned):
+ * org.texi: Include "org-version.inc" instead of
+ "git-describe.texi".
+
+ * org.texi: Remove @set for VERSION and DATE and do an @include
+ git-describe.texi instead.
Not relevant since Paul already did it 2012-09-01:
+ * org-id.el: Do not use (random t), we just want a new random
+ number, not a re-seeding of the PRNG for which (random t) doesn't
+ provide enough entropy anyway. Even if (random) would always
+ produce the same sequence, the other components going into the MD5
+ hash ensure that the result will be unique.
No ChangeLog entries:
=== modified file 'etc/org/OrgOdtContentTemplate.xml'
=== modified file 'etc/org/OrgOdtStyles.xml'
=== modified file 'etc/refcards/orgcard.tex'
It's weird to see this as a constant (rather than something related to
the installation prefix), since it won't be correct for many
installations (but I did not check how it is actually used):
;;;###autoload
(defconst org-odt-data-dir "/usr/share/emacs/etc/org"
"The location of ODT styles.")
Also, have you considered having a separate org-loaddefs.el, for
autoloads that are not relevant until org.el is loaded?
next parent reply other threads:[~2012-10-01 0:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1TILGf-0007Kr-Mg@vcs.savannah.gnu.org>
2012-10-01 0:26 ` Glenn Morris [this message]
2012-10-01 6:19 ` /srv/bzr/emacs/trunk r110286: Sync Org 7.9.2 from the commit tagged "release_7.9.2" in Org's Git repo Bastien
2012-10-01 7:03 ` Glenn Morris
2012-10-01 13:22 ` Bastien
2012-10-01 16:47 ` Achim Gratz
2012-10-01 17:39 ` Glenn Morris
2012-10-01 17:59 ` Achim Gratz
2012-10-01 18:04 ` Glenn Morris
2012-10-02 12:58 ` Bastien
2012-10-02 17:05 ` Achim Gratz
2012-10-02 17:17 ` Bastien
2012-10-02 17:34 ` Achim Gratz
2012-10-02 17:43 ` Glenn Morris
2012-10-02 17:51 ` Achim Gratz
2012-10-02 17:58 ` Glenn Morris
2012-10-02 18:16 ` Achim Gratz
2012-10-02 18:58 ` Glenn Morris
2012-10-03 15:46 ` Achim Gratz
2012-10-03 17:35 ` Stefan Monnier
2012-10-03 17:54 ` Achim Gratz
2012-10-03 18:30 ` Stefan Monnier
2012-10-01 18:02 ` Achim Gratz
2012-10-02 12:56 ` Bastien
2012-10-02 17:03 ` Achim Gratz
2012-10-02 17:17 ` Bastien
2012-10-02 17:25 ` Achim Gratz
2012-10-02 17:44 ` Bastien
2012-10-02 18:12 ` Achim Gratz
2012-10-03 7:08 ` Bastien
2012-10-03 7:48 ` Achim Gratz
2012-10-03 10:24 ` Bastien
2012-10-01 18:07 ` Jambunathan K
2012-10-02 13:03 ` Bastien
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mn391z6nql.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=bzg@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.