unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: todo-mode doc bug
Date: Wed, 27 Apr 2016 12:52:31 +0300	[thread overview]
Message-ID: <83zisfxtsw.fsf@gnu.org> (raw)
In-Reply-To: <87mvofv220.fsf@gmx.net> (message from Stephen Berman on Wed, 27 Apr 2016 11:22:31 +0200)

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: emacs-devel@gnu.org
> Date: Wed, 27 Apr 2016 11:22:31 +0200
> 
> It didn't occur to me that you meant that specific message

I didn't.  I haven't read the discussion until you said it didn't
contain anything useful.  I just gave the advice because referencing
the thread is cheap and can never cause any information loss.  It's
just something I learned from experience, that's all.

> I guess the only repair it to revert my commit and then make a new
> one with the reference.  Should I do that?

It doesn't look to me important enough for such troubles.

Thanks.



      reply	other threads:[~2016-04-27  9:52 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
2016-04-27  8:50                   ` Eli Zaretskii
2016-04-27  9:22                     ` Stephen Berman
2016-04-27  9:52                       ` Eli Zaretskii [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=83zisfxtsw.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 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).