From: Tobias Geerinckx-Rice <me@tobias.gr>
To: guix-devel@gnu.org
Subject: Re: Please merge guix-patches bug: 36789-36800
Date: Wed, 24 Jul 2019 20:47:21 +0200 [thread overview]
Message-ID: <87k1c7i81y.fsf@nckx> (raw)
In-Reply-To: <CAJ3okZ2HpFUEZoDNuJV=EMH-E5eMA+TbVFp7EO2yYoSrCK+GYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]
Zimoun,
zimoun 写道:
> Please merge guix-patches bug: 36789-36800
You can perform actions like this yourself by sending mail to
control@debbugs.gnu.org. Here's some documentation[0] and a
caveat[1].
> I have missed how it works. I simply did:
>
> git send-email -11 --cover-letter --annotate
> --to=guix-patches@gnu.org
>
> and it is incorrect. Oups!
Indeed!
> What is the correct command line to first obtain a debbug number
> and
> second to send the series to this number ?
I was certain that this was in the manual, but I can't find it
quickly. Hm.
What I do is to just manually write a cover letter in my MUA, send
it to guix-patches@, and wait for the response with the bug
number. I have to keep an eye on my inbox anyway, so I don't see
the point of doing that on the command line.
Then I git send-email --to=nnnnn@debbugs.gnu.org.
> Thank you in advance. And sorry again for the mistake.
That's quite all right. Thank you for immediately addressing it!
Kind regards,
T G-R
[0]: https://debbugs.gnu.org/server-control.html
[1]: In practice, there are hard limits on the length of these
commands (and possibly the number of commands in one mail). I
once sent a (scripted) ‘merge a b c d … j k l’ request and
debbugs (silently) merged only the first n items. I forget what n
was.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-07-24 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 18:29 Please merge guix-patches bug: 36789-36800 zimoun
2019-07-24 18:47 ` Tobias Geerinckx-Rice [this message]
2019-07-24 19:31 ` zimoun
2019-07-24 19:55 ` Tobias Geerinckx-Rice
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=87k1c7i81y.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-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/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).