From: Noam Postavsky <npostavs@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 33225@debbugs.gnu.org, "garreau, alexandre" <galex-713@galex-713.eu>
Subject: bug#33225: [debbugs.el] Don't send control message immediately
Date: Mon, 01 Apr 2019 18:59:59 -0400 [thread overview]
Message-ID: <878swtib68.fsf@gmail.com> (raw)
In-Reply-To: <87bm1pibr3.fsf@gmail.com> (Noam Postavsky's message of "Mon, 01 Apr 2019 18:47:28 -0400")
>> There's nothing left I could nitpick, so pls commit :-)
>
> Okay, sorted and pushed.
>
> [1: be4e402f9]: 2019-04-01 18:45:04 -0400
> New command debbugs-control-make-message (Bug#33225)
> https://git.savannah.gnu.org/cgit/emacs/elpa.git/commit/?id=be4e402f92ba3c2326f0f71afdcc5dde66546624
Ugh, of course I discover a mistake just after pushing (in fact, while
using it to create the previous message). I forgot to check for a nil
version in a couple of cases.
[2: 54678808c]: 2019-04-01 18:54:10 -0400
Fix previous change for version-less commands
https://git.savannah.gnu.org/cgit/emacs/elpa.git/commit/?id=54678808cdb18da080553e18ce5d806cd1659c82
next prev parent reply other threads:[~2019-04-01 22:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 12:29 bug#33225: [debbugs.el] Don't send control message immediately Noam Postavsky
2018-11-01 14:28 ` Garreau, Alexandre
2018-11-02 10:30 ` Michael Albinus
2018-11-02 10:23 ` Michael Albinus
2019-01-04 14:38 ` Michael Albinus
2019-02-27 8:45 ` Michael Albinus
2019-02-28 1:10 ` Noam Postavsky
2019-02-28 7:10 ` Michael Albinus
2019-03-30 2:43 ` Noam Postavsky
2019-03-31 10:21 ` Michael Albinus
2019-03-31 21:27 ` Noam Postavsky
2019-04-01 7:35 ` Michael Albinus
2019-04-01 13:34 ` Noam Postavsky
2019-04-01 14:52 ` Michael Albinus
2019-04-01 22:47 ` Noam Postavsky
2019-04-01 22:59 ` Noam Postavsky [this message]
2019-04-02 5:52 ` Michael Albinus
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=878swtib68.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=33225@debbugs.gnu.org \
--cc=galex-713@galex-713.eu \
--cc=michael.albinus@gmx.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 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.