From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: todo-mode doc bug (was: [Emacs-diffs] emacs-25 e5c17f4: Fix todo-mode category movement)
Date: Mon, 25 Apr 2016 13:03:09 +0300 [thread overview]
Message-ID: <83r3du2eg2.fsf@gnu.org> (raw)
In-Reply-To: <87inz6ui4g.fsf@gmx.net> (message from Stephen Berman on Mon, 25 Apr 2016 11:56:15 +0200)
> From: Stephen Berman <stephen.berman@gmx.net>
> Date: Mon, 25 Apr 2016 11:56:15 +0200
>
> I'm not sure what counts as trivial, and now have reason to ask for
> clarification. Specifically, I noticed that the doc string of
> `todo-show' is in part obsolete and incorrect -- in fact, it already was
> when I initially committed this version of todo-mode to the Emacs
> repository, because I had failed to update the doc string after making
> the change in ea3ae33b5b94bf095c52f279887009e8fb71a9df prior to the
> initial commit. (In contrast, the Todo mode Info manual contains the
> correct information.) Is it ok for me to commit the following doc
> string change to emacs-25, and also dispense with a bug report?
Doc string corrections are always okay (assuming you are sure they are
correct). I have no opinion about closing the bug.
Thanks.
next prev parent reply other threads:[~2016-04-25 10:03 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r3du2eg2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen.berman@gmx.net \
/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.