From: Saku Laesvuori <saku@laesvuori.fi>
To: Edouard Klein <edou@rdklein.fr>
Cc: Simon Tournier <zimon.toutoune@gmail.com>, guix-devel@gnu.org
Subject: Re: Can we provide another UI for patches than just email ?
Date: Sat, 16 Sep 2023 09:57:33 +0300 [thread overview]
Message-ID: <qcoocsno7a3ch6icfwjhduufqial2kvrzpch6h6txmweqtqg4j@jvgi2fwzwyzp> (raw)
In-Reply-To: <874jjw1rj8.fsf@rdklein.fr>
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
> I'd like to be part of the solution, so Saku, I'd like to help
> write the putative scripts you talk about. The main difficulty I see is
> that they need to be configured to be able to send and receive email on
> the user's behalf.
That could probably be done via git send-email. I think the hardest
thing is working around debbugs. One idea I have is to first create a
branch with a name like <description>-not-submitted, then somehow get the
issue number after sending the first email and then rename the branch to
<description>-<issue-number> and either add a conditional git configuration
rule[1] that sets the sendemail-to to the corresponding address or use
that information from the script. Maybe mumi already does most of this,
I haven't tried it yet (but I probably should).
[1]: https://www.git-scm.com/docs/git-config#_conditional_includes
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-09-16 6:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 8:51 Can we provide another UI for patches than just email ? Edouard Klein
2023-09-14 9:37 ` Saku Laesvuori
2023-09-14 17:48 ` Simon Tournier
2023-09-14 18:57 ` Edouard Klein
2023-09-15 10:07 ` Simon Tournier
2023-09-16 6:57 ` Saku Laesvuori [this message]
2023-09-17 2:18 ` Maxim Cournoyer
2023-09-16 22:19 ` Liliana Marie Prikler
2023-09-17 11:10 ` Simon Tournier
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=qcoocsno7a3ch6icfwjhduufqial2kvrzpch6h6txmweqtqg4j@jvgi2fwzwyzp \
--to=saku@laesvuori.fi \
--cc=edou@rdklein.fr \
--cc=guix-devel@gnu.org \
--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).