From: Ricardo Wurmus <rekado@elephly.net>
To: 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: Sat, 04 Jun 2022 13:00:43 +0200 [thread overview]
Message-ID: <87ee04667r.fsf@elephly.net> (raw)
In-Reply-To: <86sgbhz3fe.fsf@gmail.com>
zimoun <zimon.toutoune@gmail.com> writes:
> For example <http://issues.guix.gnu.org/33899#16>. The number #16 is
> really difficult to guess. :-)
>
> Instead, it is easy to get the Message-ID. (Using emacs-notmuch, only
> hit the key ’ci’) Therefore, it could be nice to be able to provide
> e.g., the URL:
>
> <issues.guix.gnu.org/HAv_FWZRa_dCADY6U07oX-E2vTrtcxk8ltkpfvTpYCsIh4O5PuItHGIh6w-g5GGmoqVEfkjDUOplpUErdGEPAiFYdrjjDhwd9RJ4OyjjGgY=@hector.link>
>
> redirecting to <http://issues.guix.gnu.org/33899#16>. And maybe the
> current webpage could provide the Message-ID, easy to copy and then
> paste in my email reader.
This is now implemented in mumi.
Once delpoyed to issues.guix.gnu.org you can visit
https://issues.guix.gnu.org/msgid/HAv_FWZRa_dCADY6U07oX-E2vTrtcxk8ltkpfvTpYCsIh4O5PuItHGIh6w-g5GGmoqVEfkjDUOplpUErdGEPAiFYdrjjDhwd9RJ4OyjjGgY=@hector.link
and it would redirect to https://issues.guix.gnu.org/33899. It doesn’t
yet jump to the correct message number, but that’s easy to implement.
(I only had time for one little hack.)
--
Ricardo
next prev parent reply other threads:[~2022-06-04 11:04 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 [this message]
2022-06-04 22:12 ` Ricardo Wurmus
2022-06-05 10:28 ` zimoun
2022-06-06 11:43 ` Arun Isaac
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=87ee04667r.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=kyle@kyleam.com \
--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).