From: Danny Milosavljevic <dannym@scratchpost.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 26840@debbugs.gnu.org, Kei Kebreau <kei@openmailbox.org>
Subject: bug#26840: [PATCH 2/3] gnu: go-1.4: Add missing module imports.
Date: Fri, 12 May 2017 00:29:37 +0200 [thread overview]
Message-ID: <20170512002937.1991fe41@scratchpost.org> (raw)
In-Reply-To: <874lwrjatf.fsf@fastmail.com>
On Fri, 12 May 2017 00:19:40 +0200
Marius Bakke <mbakke@fastmail.com> wrote:
> Alternatively, email control@debbugs.gnu.org with "close 12345".
>
> I see it also takes a "version" parameter, e.g. "close 12345 aaabbbccc".
Nice!
I wonder whether it would be possible to have an auto-closer job?
I think it's not really useful to have to specify that the bug is fixed twice - once in the commit message and once in the bug report.
If we wanted to automate it, who could we ask about it?
next prev parent reply other threads:[~2017-05-11 22:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 19:55 bug#26841: [PATCH 0/3] core-updates: more fixes for missing dependencies for %modify-phases Sergei Trofimovich
2017-05-08 19:55 ` bug#26842: [PATCH 1/3] gnu: zip: add missing '#:modules' imports Sergei Trofimovich
2017-05-11 19:53 ` Kei Kebreau
2017-05-08 19:55 ` bug#26840: [PATCH 2/3] gnu: go-1.4: Add missing module imports Sergei Trofimovich
2017-05-11 19:57 ` Kei Kebreau
2017-05-11 21:06 ` Danny Milosavljevic
2017-05-11 21:25 ` Kei Kebreau
2017-05-11 21:28 ` Leo Famulari
2017-05-11 22:19 ` Marius Bakke
2017-05-11 22:29 ` Danny Milosavljevic [this message]
2017-05-12 4:26 ` Leo Famulari
2017-05-12 21:52 ` Ludovic Courtès
2017-05-12 23:05 ` Kei Kebreau
2017-05-13 13:08 ` Ludovic Courtès
2017-05-08 19:55 ` bug#26843: [PATCH 3/3] gnu: sbcl: " Sergei Trofimovich
2017-05-09 15:53 ` bug#26841: [PATCH 0/3] core-updates: more fixes for missing dependencies for %modify-phases Danny Milosavljevic
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=20170512002937.1991fe41@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=26840@debbugs.gnu.org \
--cc=kei@openmailbox.org \
--cc=mbakke@fastmail.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 external index
https://git.savannah.gnu.org/cgit/guix.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.