From: zimoun <zimon.toutoune@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Please merge guix-patches bug: 36789-36800
Date: Wed, 24 Jul 2019 21:31:11 +0200 [thread overview]
Message-ID: <CAJ3okZ0VA9+zYN2nXzd+G47bKrBKMcUPy54yH_7j7wM4mJV1-A@mail.gmail.com> (raw)
In-Reply-To: <87k1c7i81y.fsf@nckx>
Hi Tobias,
Thank you for your quick answer.
On Wed, 24 Jul 2019 at 20:47, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
> 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 did not know. I thought that only person with super power could do that.
So I will do.
However, I am not sure to understand how the merge needs to be ordered.
I have tried with 36789 and 36790.
> 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.
If I understand well, the basic workflow is:
git format-patch -N --cover-letter -o patches
edit patches/0000-cover-letter.patch
# send as you want patches/0000-cover-letter.patch to guix-patches@
rm patches/0000-cover-letter.patch
# wait the bug number
git send-email --to=nnnnn@debbugs.gnu.org patches/*.patch
Right?
> [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.
Thank you.
All the best,
simon
next prev parent reply other threads:[~2019-07-24 19:31 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
2019-07-24 19:31 ` zimoun [this message]
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=CAJ3okZ0VA9+zYN2nXzd+G47bKrBKMcUPy54yH_7j7wM4mJV1-A@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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).