all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>, jgart <jgart@dismail.de>
Cc: guix-devel@gnu.org
Subject: Re: Guix packaging meetup: Saturday 27 November
Date: Thu, 25 Nov 2021 23:11:03 +0100	[thread overview]
Message-ID: <864k7zvqbs.fsf@gmail.com> (raw)
In-Reply-To: <87bl28q6h7.fsf@nckx>

Hi,

On Thu, 25 Nov 2021 at 22:01, Tobias Geerinckx-Rice <me@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.fsf@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.fsf@yeeloong.lan/

…end)


Cheers,
simon


  parent reply	other threads:[~2021-11-25 22:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25 11:11 jgart
2021-11-25 20:52 ` jgart
2021-11-25 21:01   ` Guix packaging meetup: Saturday 27 November Tobias Geerinckx-Rice
2021-11-25 21:26     ` jgart
2021-11-25 22:11     ` zimoun [this message]
2021-11-27  9:40     ` Tobias Platen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=864k7zvqbs.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.