unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: Ricardo Wurmus <rekado@elephly.net>, zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>, Kyle Meyer <kyle@kyleam.com>
Subject: Re: Mummi wishlist: API using Message-ID
Date: Mon, 06 Jun 2022 17:13:25 +0530	[thread overview]
Message-ID: <87a6aqm2zm.fsf@systemreboot.net> (raw)
In-Reply-To: <87ee04667r.fsf@elephly.net>


> Once delpoyed to issues.guix.gnu.org you can visit
>
> https://issues.guix.gnu.org/msgid/HAv_FWZRa_dCADY6U07oX-E2vTrtcxk8ltkpfvTpYCsIh4O5PuItHGIh6w-g5GGmoqVEfkjDUOplpUErdGEPAiFYdrjjDhwd9RJ4OyjjGgY=@hector.link

This is great news! Using this, we should be able to implement a `mumi
send-email' command to easily send N patches to a new issue. Here is
how `mumi send-email' might be implemented:

1. Generate patches with `git format-patch --thread' so that there is a
   Message-ID header.

2. Send the first patch to guix-patches@gnu.org.

3. Poll https://issues.guix.gnu.org/<message-id> to see if the first
   patch has reached Debbugs/Mumi. Find the issue number of the new
   issue that was created.

4. Send the remaining patches to the new issue.

Regards,
Arun


  parent reply	other threads:[~2022-06-06 12:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16 23:51 Mummi wishlist: API using Message-ID zimoun
2020-09-17 10:01 ` Ricardo Wurmus
2020-09-17 10:38   ` zimoun
2020-09-17 11:33     ` Ricardo Wurmus
2020-09-18  5:44       ` Arun Isaac
2020-09-18  3:53     ` Kyle Meyer
2020-09-18 16:46       ` Kyle Meyer
2022-06-04 11:00 ` Ricardo Wurmus
2022-06-04 22:12   ` Ricardo Wurmus
2022-06-05 10:28   ` zimoun
2022-06-06 11:43   ` Arun Isaac [this message]
2022-06-06 12:03     ` Ricardo Wurmus
2022-06-06 12:17       ` Arun Isaac
2022-06-06 12:30       ` Julien Lepiller
2022-06-08 20:14         ` Arun Isaac

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=87a6aqm2zm.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=guix-devel@gnu.org \
    --cc=kyle@kyleam.com \
    --cc=rekado@elephly.net \
    --cc=zimon.toutoune@gmail.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 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).