From: Achim Gratz <Stromeko@NexGo.DE>
To: emacs-devel@gnu.org
Subject: Re: Should we use `symbol' or 'symbol' in Emacs change logs?
Date: Fri, 30 May 2014 06:43:52 +0000 (UTC) [thread overview]
Message-ID: <loom.20140530T084148-801@post.gmane.org> (raw)
In-Reply-To: tt7g54s6p2.fsf@fencepost.gnu.org
Glenn Morris <rgm <at> gnu.org> writes:
> > Then you might want to document it somewhere
>
> Bam, done in trunk r117195.
Thanks.
> (Personally I think "every existing ChangeLog in Emacs" was
> documentation enough.)
If that was indeed so clear cut, I wouldn't have asked.
Regards,
Achim.
prev parent reply other threads:[~2014-05-30 6:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 17:10 Should we use `symbol' or 'symbol' in Emacs change logs? Bastien
2014-05-29 18:29 ` Stefan Monnier
2014-05-29 18:49 ` Bastien
2014-05-29 19:20 ` Achim Gratz
2014-05-29 19:52 ` Glenn Morris
2014-05-29 20:26 ` Stefan Monnier
2014-05-29 20:33 ` Bastien
2014-05-29 21:48 ` Paul Eggert
2014-05-30 6:43 ` Achim Gratz [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=loom.20140530T084148-801@post.gmane.org \
--to=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).