From: "(" <paren@disroot.org>
To: "Wojtek Kosior" <koszko@koszko.org>, "zimoun" <zimon.toutoune@gmail.com>
Cc: <help-guix@gnu.org>
Subject: Re: program prepared with `guix pack` unusable by end users
Date: Thu, 13 Oct 2022 18:34:08 +0100 [thread overview]
Message-ID: <CNKZ5D4COPR9.3J8Y2Y4LMY02J@guix-framework> (raw)
In-Reply-To: <20221013182027.2044d8ff@koszkonutek-tmp.pl.eu.org>
Heya,
On Thu Oct 13, 2022 at 5:20 PM BST, Wojtek Kosior via wrote:
> It took me a couple of minutes to understand what you're talking about. Indeed, instead of copy-pasting the <help-guix@gnu.org> address I clicked "Reply" on some random email from Guix mailing list and changed the subject. For years I've been certain that messages are categorized into threads by their subject. Now, as you wrote this, I assume there must be some thread meta-data that is invisibly sent by our user agents when we use "Reply" or "Reply all".
Yes, the In-Reply-To: header :)
-- (
next prev parent reply other threads:[~2022-10-13 17:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 16:20 program prepared with `guix pack` unusable by end users Wojtek Kosior via
2022-10-13 17:34 ` ( [this message]
2022-10-14 7:33 ` zimoun
2022-10-14 9:09 ` Wojtek Kosior via
2022-10-14 11:00 ` zimoun
2022-10-17 13:36 ` Wojtek Kosior via
2022-10-26 7:23 ` Wojtek Kosior via
2022-10-26 19:55 ` Csepp
2022-10-27 16:59 ` Maxim Cournoyer
2022-10-27 17:28 ` Wojtek Kosior via
2022-10-28 15:38 ` Maxim Cournoyer
-- strict thread matches above, loose matches on Subject: below --
2022-10-13 6:26 Greetd autologin? kiasoc5
2022-10-13 6:33 ` (
2022-10-13 7:17 ` program prepared with `guix pack` unusable by end users Wojtek Kosior via
2022-10-13 8:26 ` (
2022-10-13 9:51 ` Wojtek Kosior via
2022-10-13 13:19 ` zimoun
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=CNKZ5D4COPR9.3J8Y2Y4LMY02J@guix-framework \
--to=paren@disroot.org \
--cc=help-guix@gnu.org \
--cc=koszko@koszko.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.
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).