Hi,
On Thu, 25 Nov 2021 at 22:01, Tobias Geerinckx-Rice <m...@tobias.gr> wrote:
> Thank you for the invitation!
Cool! I say each time to my self: next I will attend… and life happens.
Anyway, next time I will be there. :-)
(Off-topic ramblings…
> Threading is (or should be) based on message IDs, although some
> archivers will use the subject as an additional heuristic.
That’s why GNU web front-end use numbering instead of Message IDs. :-p
For instance the message I am replying is the 184th sent to guix-devel
for Nov. 2021. Since it is easy to know this information (extrinsic),
it is obvious to link the archive:
https://lists.gnu.org/archive/html/guix-devel/2021-11/msg00184.html
Sigh. Why am I sarcastic here? ;-)
When using Notmuch (or any descent email client), it is trivial to get
the Message ID (press just ’cI’ with emacs-notmuch):
87bl28q6h7.fsf@nckx
Knowing this information, other tools use that for indexing, for
instance ’public-inbox’:
https://yhetil.org/guix/87bl28q6h7.fsf@nckx
(emacs-notmuch: ’cl’ correctly configured add the URL in the kill ring,
ready for pasting wherever)
I do not know if GNU Mailman with HyperKitty is serving URLs archive
containing Message-ID (intrinsic). On a side note, I find interesting
that the GNU project does not deploy a recent release of a GNU tool for
friendly collaboration; because the version of GNU Mailman behind
<https://lists.gnu.org/> is more than outdated.
What depends on Guix project is the numbering of the front-end Mumi
(really nice and friendly front-end for Debbugs), as with:
https://issues.guix.gnu.org/17150#3
the 4th message about bug 17150. Where it could nice to have in
addition:
https://issues.guix.gnu.org/87lhvqm179....@yeeloong.lan
(I found the message ID using this: M-x debbugs-gnu-bugs 17150 then pick
the message then M-x gnus-summary-show-raw-article and grep Message-ID
which can be automated and maybe included by Emacs Gnus, dunno.)
For instance, ’public-inbox’:
https://yhetil.org/guix/87lhvqm179....@yeeloong.lan/
…end)
Cheers,
simon
