From: Federico <federicotedin@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31039@debbugs.gnu.org
Subject: bug#31039: 27.0.50; allow silencing auto-save
Date: Sat, 11 Aug 2018 15:20:15 -0300 [thread overview]
Message-ID: <CAA8GjPmoKno1M62Cf38f9RyDgHO96LjOXAXLbZANEA5qYV1ZKA@mail.gmail.com> (raw)
In-Reply-To: <834lg1mcwb.fsf@gnu.org>
Thanks Eli, I've taken a look at the commit and noted the corrections
you listed. Also, good to know about the copyright assignment.
On Sat, Aug 11, 2018 at 7:11 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Sat, 11 Aug 2018 12:31:34 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: 31039-done@debbugs.gnu.org, npostavs@gmail.com, aaronjensen@gmail.com
>>
>> A few minor nits for your future contributions:
>>
>> . For changes in the manuals, the name of the node where the change
>> is done should be mentioned in parentheses, as if it were a
>> function.
>> . Please make sure the NEWS entries are filled according to the
>> default setting of fill-column (use M-q to do that).
>> . It is preferable to explicitly mention the new functions/variables
>> in the log entries for NEWS and the manuals.
>
> Sorry, 2 more:
>
> . Always mention the bug number in the log entry.
> . When you add a new customizable option, always mark it with the
> first Emacs version where the option will appear, in this case
> 27.1.
>
> Thanks.
prev parent reply other threads:[~2018-08-11 18:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 9:06 bug#31039: 27.0.50; allow silencing auto-save Aaron Jensen
2018-08-04 0:51 ` Federico
2018-08-06 2:43 ` Noam Postavsky
2018-08-06 14:56 ` Eli Zaretskii
2018-08-06 15:05 ` Eli Zaretskii
2018-08-06 23:02 ` Federico
2018-08-07 14:54 ` Eli Zaretskii
2018-08-07 18:36 ` Federico
2018-08-11 16:10 ` Aaron Jensen
2018-08-11 9:31 ` Eli Zaretskii
2018-08-11 10:11 ` Eli Zaretskii
2018-08-11 18:20 ` Federico [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA8GjPmoKno1M62Cf38f9RyDgHO96LjOXAXLbZANEA5qYV1ZKA@mail.gmail.com \
--to=federicotedin@gmail.com \
--cc=31039@debbugs.gnu.org \
--cc=eliz@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.