unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Reiner Steib <Reiner.Steib@gmx.de>
Cc: dann@ics.uci.edu, emacs-devel@gnu.org
Subject: Re: [reinersteib+gmane@imap.cc: 23.0.50; VC; log-view-diff -> vc-version-diff undefined]
Date: Mon, 29 Oct 2007 05:21:23 -0400	[thread overview]
Message-ID: <E1ImQoF-00004y-GB@fencepost.gnu.org> (raw)
In-Reply-To: <v9ejff8hhn.fsf@marauder.physik.uni-ulm.de> (message from Reiner Steib on Sun, 28 Oct 2007 15:02:28 +0100)

    Already within one day after my initial report, Stefan answered that
    it's fixed and I confirmed this (both on the list).

I am glad that it was fixed quickly.  Are you trying to suggest I
ought not to have sent the message yesterday, because I should have
REMEMBERED seeing those messages?

I wish I had such a good memory, but I don't.  My unaided memory is
not adequate for keeping track of the status of so many bugs.  So I
use various computer aids.  One is FOR-RELEASE.  The other is a system
that will tell me if a message gets no answer in a certain period.  I
send the message, and ask people to ack when it is dealt with.  If the
message gets no reply, I do not forget about the issue.

If you see such a message, please consider it a bug tracking system.
If the bug is already fixed, please answer the message saying so.
That is the way to inform my bug tracking system to "close the ticket".

  reply	other threads:[~2007-10-29  9:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-27 13:57 [reinersteib+gmane@imap.cc: 23.0.50; VC; log-view-diff -> vc-version-diff undefined] Richard Stallman
2007-10-27 16:07 ` Dan Nicolaescu
2007-10-28 13:50   ` Richard Stallman
2007-10-28 14:02     ` Reiner Steib
2007-10-29  9:21       ` Richard Stallman [this message]
2007-10-29 19:42         ` bug tracking (was: [reinersteib+gmane@imap.cc: 23.0.50; VC; log-view-diff -> vc-version-diff undefined]) Reiner Steib
2007-10-30  5:24           ` Richard Stallman

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=E1ImQoF-00004y-GB@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=Reiner.Steib@gmx.de \
    --cc=dann@ics.uci.edu \
    --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).