all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: R?diger Sonderfeld <ruediger@c-plusplus.de>
Cc: 11386@debbugs.gnu.org
Subject: bug#11386: C++11 support: C++ mode gets (temporarily) confused by	edits to convert "> >" to ">>" in templates
Date: 18 Nov 2014 21:15:19 -0000	[thread overview]
Message-ID: <20141118211519.65986.qmail@mail.muc.de> (raw)
In-Reply-To: <mailman.13959.1416330148.1147.bug-gnu-emacs@gnu.org>

Guten Abend, Ruediger.

In article <mailman.13959.1416330148.1147.bug-gnu-emacs@gnu.org> you wrote:
> tags 11386 fixed

> Should be fixed in 66bb9533fc77963c495de7f33ec6dc8e4d342a55

OUTCH!!!

Any chance you could be a little more informative with messages like this,
please?

The message as it stands suggests "I have just committed a fix as revision
66bb95...".  The id 66bb95..., like all ids in git, carries no context,
no age, no nothing.

Better would have been to use the "present perfect" tense: "Should have
been fixed in 66bb95...", which would have placed the action of fixing
in the non-immediate past.

Better still would have been to give details of the fix, something like
"Should have been fixed in 66bb953... by Alan Mackenzie in August, title
line "Make ">>" act as double template ender in C++ Mode."".

Possibly the best thing of all would have been to construct an Eric
Raymond style commit identifier, but I haven't got the syntax memorised
yet.

Any of these would have prevented me errupting in uncalled-for panic and
fury.

Thanks!

-- 
Alan Mackenzie (Nuremberg, Germany).








      parent reply	other threads:[~2014-11-18 21:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-30 21:05 bug#11386: C++11 support: C++ mode gets (temporarily) confused by edits to convert "> >" to ">>" in templates James Dennett
2014-11-18 17:00 ` Rüdiger Sonderfeld
     [not found] ` <mailman.13959.1416330148.1147.bug-gnu-emacs@gnu.org>
2014-11-18 21:15   ` Alan Mackenzie [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=20141118211519.65986.qmail@mail.muc.de \
    --to=acm@muc.de \
    --cc=11386@debbugs.gnu.org \
    --cc=ruediger@c-plusplus.de \
    /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.