unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Lassieur" <clement@lassieur.org>
To: Hartmut Goebel <h.goebel@goebel-consult.de>
Cc: 26352-close@debbugs.gnu.org
Subject: bug#26352: close
Date: Wed, 12 Apr 2017 15:34:17 +0200	[thread overview]
Message-ID: <87h91t3g2u.fsf@lassieur.org> (raw)
In-Reply-To: <58EDE14F.3000807@goebel-consult.de>

Hartmut Goebel <h.goebel@goebel-consult.de> writes:

> close

In order to close a bug, you need either to:

  - send a message to 26352-close@debbugs.gnu.org (which I just did),
  - send a message to control@debbugs.gnu.org, with "close 26352" as
    content.

The second method is quiet: people subscribing to the list won't receive
it, which is better IMHO if there is no content in the message.

See https://debbugs.gnu.org/server-refcard.html.

To see if it is really closed, you can have a look at:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26352.

  reply	other threads:[~2017-04-12 13:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03 18:54 bug#26352: [PATCH 0/3] Update KDE Frameworks to 5.32 Hartmut Goebel
2017-04-03 18:56 ` bug#26352: [PATCH 1/3] gnu: Update networkmanager to version 1.6.2 Hartmut Goebel
2017-04-03 18:56   ` bug#26352: [PATCH 2/3] gnu: Update phonon to 4.9.1 Hartmut Goebel
2017-04-03 18:56   ` bug#26352: [PATCH 3/3] gnu: Update kde-frameworks to 5.32.0 Hartmut Goebel
2017-04-10 10:04   ` bug#26352: [PATCH 1/3] gnu: Update networkmanager to version 1.6.2 Ludovic Courtès
2017-04-11 13:48     ` Hartmut Goebel
2017-04-11 15:45       ` Ludovic Courtès
2017-04-12  8:11         ` Hartmut Goebel
2017-04-12  8:11           ` bug#26352: close Hartmut Goebel
2017-04-12 13:34             ` Clément Lassieur [this message]
2017-04-03 19:12 ` bug#26352: [PATCH 4/4] gnu: kde-frameworks: No longer setenv CTEST_OUTPUT_ON_FAILURE Hartmut Goebel

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h91t3g2u.fsf@lassieur.org \
    --to=clement@lassieur.org \
    --cc=26352-close@debbugs.gnu.org \
    --cc=h.goebel@goebel-consult.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.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).