From: Karl Fogel <kfogel@red-bean.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Suggestion to indicate fixed version when closing a bug
Date: Sun, 11 Dec 2011 01:32:00 -0500 [thread overview]
Message-ID: <87aa6z4o0v.fsf@floss.red-bean.com> (raw)
In-Reply-To: <83sjkrllhh.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 11 Dec 2011 07:34:50 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Karl Fogel <kfogel@red-bean.com>
>> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>> Date: Sat, 10 Dec 2011 16:20:24 -0500
>>
>> You meant the version number ("edition", "release", whatever) of Emacs
>> in which the bug was fixed, not revision information about the change
>> that fixed it.
>>
>> The latter is what I've been (mistakenly) talking about in this thread;
>
>I've been mentioning the revision number when closing bug reports
>since quite some time ago.
Yes, and probably for exactly the reasons I took the trouble to
needlessly spell out :-).
next prev parent reply other threads:[~2011-12-11 6:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 7:57 Suggestion to indicate fixed version when closing a bug Glenn Morris
2011-12-10 8:38 ` Eli Zaretskii
2011-12-10 19:10 ` Glenn Morris
2011-12-10 19:13 ` Glenn Morris
2011-12-10 19:31 ` Lennart Borgman
2011-12-10 19:43 ` Eli Zaretskii
2011-12-10 20:55 ` Glenn Morris
2011-12-10 21:08 ` Eli Zaretskii
2011-12-10 21:17 ` Glenn Morris
2011-12-10 21:20 ` Karl Fogel
2011-12-11 5:34 ` Eli Zaretskii
2011-12-11 6:32 ` Karl Fogel [this message]
2011-12-11 17:37 ` Stephen J. Turnbull
2011-12-10 21:17 ` Karl Fogel
2011-12-10 21:20 ` Glenn Morris
2011-12-10 22:53 ` Glenn Morris
2011-12-11 5:33 ` Eli Zaretskii
2011-12-12 0:06 ` Glenn Morris
2011-12-12 8:40 ` Lars Magne Ingebrigtsen
2011-12-10 19:28 ` Karl Fogel
2011-12-10 19:44 ` Eli Zaretskii
2011-12-12 16:41 ` Stefan Monnier
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=87aa6z4o0v.fsf@floss.red-bean.com \
--to=kfogel@red-bean.com \
--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 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.