lists.sr.ht is the sr.ht mailing list service.
See also:
We have some resources for you:
If you plan on contributing patches, we also have these guides:
The following sections document various features of lists.sr.ht.
You may post to a list that you have posting permissions on by writing a
plaintext email to ~user/list-name@lists.sr.ht. If your MTA doesn't support
characters like ~ and / in emails, please write to postmaster@your-mta.com
asking them to fix the bug, then use u.username.list-name@lists.sr.ht instead.
You may subscribe to any list by emailing
~user/list-name+subscribe@lists.sr.ht. You may unsubscribe with
+unsubscribe. You may post new threads to this list by writing to the address
with no + command.
Email replies to patchset threads can include a custom header,
X-Sourcehut-Patchset-Update to update the status of the patchset to
PROPOSED, NEEDS_REVISION, SUPERSEDED, APPROVED, REJECTED, or
APPLIED.
Your dashboard shows you recent emails on mailing lists you're subscribed to. You can reply to one by clicking the author's name, or view the thread by clicking the subject.
Your public profile page shows a feed of emails authored by you, as well as a list of mailing lists you administrate. Like the dashboard, you can reply to emails by clicking the authors name and view the thread by clicking the subject.
Each list shows a list of archives, sorted by which has seen the most recent activity. In each thread's heading, you can see the number of participants, number of replies, and subject of the initial message. Click the subject to see the full thread.
The search bar allows you to search list archives. Optional filters include:
from: the author of the message. Use me to search for messages sent by
yourselfis:patch only show messages that contain a patchIn-Reply-To: show messages that are replies to a given message IDmessage-id: find message with a given message IDSurround search terms with double-quotes to return exact matches.
Email threads can become trees as participants reply to different messages. In the simple case of a linear thread, you will see replies written linearly. However, if a thread becomes split, you may see several linear trees of discussion form.
To reply to a message, click the author's email address.
Additionally, you can download raw messages from each thread, either
individually or as a whole in an mbox format. This is useful for applying
submitted patches via git am/hg import among other uses.
Access raw individual messages by clicking on "Details" and following the link there.
Access Mbox files by clicking on "Export thread (mbox)" in the sidebar.
List access controls are available in your list settings, accessed with the "List settings" button on the archive page. The controls are fine-grained enough to support many access scenarios, here are some examples:
A list that only you can write to is useful for announcements. To create such a list, remove all users' "post" and "reply" permissions, to prevent them from submitting. Owners are always able to post, of course. You could optionally leave the "reply" permission enabled to allow people to respond to announcements, but beware that their responses will be sent out to all subscribers, which is usually undesirable for low-volume announcement lists.
If you want a mailing list where people can write to you about security vulnerabilities in your software, you can remove the "browse" permission without removing the "post" or "reply" permissions from the list. This will allow people to send emails to the list, but not view the archives or subscribe.
commit 93f98ec8f78010de4f1ef9edc6b89c11afce9216 Author: Conrad Hoffmann <ch@bitfehler.net> Date: 2024-09-24T17:03:25+02:00 ops: remove stale links to topology page