From: Tobias Geerinckx-Rice <me@tobias.gr>
To: jgart <jgart@dismail.de>
Cc: guix-devel@gnu.org
Subject: Re: Guix packaging meetup: Saturday 27 November
Date: Thu, 25 Nov 2021 22:01:32 +0100 [thread overview]
Message-ID: <87bl28q6h7.fsf@nckx> (raw)
In-Reply-To: <20211125155255.GC14600@gac.attlocal.net>
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
Hi jgart,
Thank you for the invitation!
jgart 写道:
> Not sure what to do at this point.
At this point, not much: you might reply to the mail with a
non-empty subject, and hope that people will reply to that one, or
that they will manually copy it when replying to your original
post. Others might add a meaningful subject of their own, as I
have tried to do.
Still, expect some untitled ‘Re:’ messages. It's not the end of
the world :-)
Mailing list archives are just that: snapshots of each message
sent to members. They do not generally offer a way to modify
recorded history[0]. They do not really track mutable state such
as ‘topics’.
Threading is (or should be) based on message IDs, although some
archivers will use the subject as an additional heuristic.
bug-guix/guix-patches are simple bug trackers built on top of
mailing lists that add such mutable state (‘bug title’, priority,
openness, etc.) but this is a separate database.
Kind regards,
T G-R
[0]: Exceptions like GDPR and ‘asking nicely to remove
embarrassing info’ exist, but are by definition exceptional and
often involve human administrator action.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-11-25 21:19 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 ` Tobias Geerinckx-Rice [this message]
2021-11-25 21:26 ` Guix packaging meetup: Saturday 27 November jgart
2021-11-25 22:11 ` zimoun
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=87bl28q6h7.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
/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.