unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Bob Proulx <bob@proulx.com>
To: Chong Yidong <cyd@gnu.org>
Cc: 3931@debbugs.gnu.org
Subject: bug#3931: close 3931 (doc of select-frame-set-input-focus and select-frame)
Date: Sun, 29 Jan 2012 15:05:07 -0700	[thread overview]
Message-ID: <20120129220507.GA7920@hysteria.proulx.com> (raw)
In-Reply-To: <877h0csb6f.fsf@gnu.org>

Hello Chong,

Chong Yidong wrote:
> close 3931
> thanks

You have used the close command to close the an open bug and did not
provide any additional information.  Please could you say why you
think this bug should be closed?  Has the bug been fixed?  Is the bug
no longer relevant?  Have you committed a change that addesses this?

Note that when you use a 'close' command to close a bug report a
simple notification of action is sent to the user who submitted the
bug.  If you choose to close a bug this way please ensure that the
user is also notified of why the action is taken.  Otherwise the bug
submitter has no information.  This can be very frustrating.  See the
documentation for the 'close' command to see that it explicitly calls
out this use case as a problem and asks maintainers to ensure that
they communicate, probably by sending a separate message, why the bug
is being closed.
  
  See the section 'close bugnumber'
  http://debbugs.gnu.org/server-control.html

Thanks,
Bob





  parent reply	other threads:[~2012-01-29 22:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877h0csb6f.fsf@gnu.org>
     [not found] ` <handler.s.C.132772495817281.transcript@debbugs.gnu.org>
2012-01-28 14:32   ` bug#3931: [debbugs-tracker] Processed: close 3931 Drew Adams
2012-01-29 22:05 ` Bob Proulx [this message]
2012-01-30  0:49   ` bug#3931: close 3931 (doc of select-frame-set-input-focus and select-frame) Chong Yidong
2012-01-30  4:58     ` Drew Adams

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=20120129220507.GA7920@hysteria.proulx.com \
    --to=bob@proulx.com \
    --cc=3931@debbugs.gnu.org \
    --cc=cyd@gnu.org \
    --cc=drew.adams@oracle.com \
    /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).