unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: todo-mode doc bug
Date: Wed, 27 Apr 2016 10:19:55 +0200	[thread overview]
Message-ID: <87r3drv4yc.fsf@gmx.net> (raw)
In-Reply-To: 83mvoi2diw.fsf@gnu.org

(Sorry for the lag in responding; I was detained by more pressing
obligations.)

On Mon, 25 Apr 2016 13:23:03 +0300 Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: emacs-devel@gnu.org
>> Date: Mon, 25 Apr 2016 12:18:33 +0200
>> 
>> >            I have no opinion about closing the bug.
>> 
>> There is no outstanding bug about this; my question was about whether it
>> is necessary to file one for this doc string change
>
> No need.  However, mentioning in the commit log the URL for the
> discussion of the issue should be considered.

This thread is the only discussion of this issue, so in the hope that
you agree with me that it isn't relevant to the doc bug per se and hence
wouldn't be appropriate to reference in the commit message, I've gone
ahead and committed the fix without such a reference.

Steve Berman



  reply	other threads:[~2016-04-27  8:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160326221513.15789.84807@vcs.savannah.gnu.org>
     [not found] ` <E1ajwUD-000485-9x@vcs.savannah.gnu.org>
2016-03-26 23:17   ` [Emacs-diffs] emacs-25 e5c17f4: Fix todo-mode category movement John Wiegley
2016-03-26 23:51     ` Stephen Berman
2016-04-03 18:22       ` John Wiegley
2016-04-25  9:56         ` todo-mode doc bug (was: [Emacs-diffs] emacs-25 e5c17f4: Fix todo-mode category movement) Stephen Berman
2016-04-25 10:03           ` Eli Zaretskii
2016-04-25 10:18             ` todo-mode doc bug Stephen Berman
2016-04-25 10:23               ` Eli Zaretskii
2016-04-27  8:19                 ` Stephen Berman [this message]
2016-04-27  8:50                   ` Eli Zaretskii
2016-04-27  9:22                     ` Stephen Berman
2016-04-27  9:52                       ` Eli Zaretskii

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=87r3drv4yc.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=eliz@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 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).