all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Another reminder about "emacs-announce" topic
Date: Wed, 18 Nov 2015 13:07:02 -0500	[thread overview]
Message-ID: <mhio4z5ghl.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <834mgmc50s.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 16 Nov 2015 17:56:03 +0200")

Eli Zaretskii wrote:

>> A final reminder that it was agreed to use the "emacs-announce" Mailman
>> topic for messages that all developers should read.
>
> Could you perhaps point to a clear description of how such a message
> should be formatted?  Also, how would a user subscribe to a "topic"?

Sorry, thought I'd explained this before, but can't find the mail now.
I think http://www.list.org/mailman-member/node29.html covers it.
For sending:

   To post on a given topic, you need to make sure that the Keywords:
   or Subject: headers in a message match the regular expression for
   that topic.

Ie:

  Keywords: emacs-announce

or:

  Subject: [emacs-announce] blah

(I guess the difference between these two is that using the Subject will
propagate into replies. Based on experience of topic drift, this is
probably not wanted.)

For reading, you only need do anything special if you only want the
topic mails, and not the vast majority of mails (which have no topic
defined):

  Log in to your member options page.
  Look for the section marked "Which topic categories would you like to
  subscribe to?" 



      reply	other threads:[~2015-11-18 18:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-15  2:14 Another reminder about "emacs-announce" topic Glenn Morris
2015-11-16 15:56 ` Eli Zaretskii
2015-11-18 18:07   ` Glenn Morris [this message]

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=mhio4z5ghl.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.