Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: garoth@gmail.com (Andrei Thorp)
Subject: [sup-talk] Fwd: [REQUEST] reply-to-list
Date: Mon, 8 Jun 2009 08:55:14 -0400	[thread overview]
Message-ID: <80055d7c0906080555h37e2b551i606e60dbdd5414f2@mail.gmail.com> (raw)
In-Reply-To: <80055d7c0906080553t41909b18j6c4a0f8fd119fa36@mail.gmail.com>

Hello there,

Today I was told to read
http://liw.iki.fi/liw/log/2003-Enemies-of-Carlotta.html.

It suggests that a good mailing client should have a reply-to-list
button since mailing lists should not add themselves as a reply-to.
The reply-to-list uses the standard List-ID header to know where to
reply to.

As far as I can tell from ?-ing around the client, sup does not have
this feature (though kudos for having a button for unsubscribe, which
I find mildly curious but cool).

I'm told that the mutt key for this is l (ell), which I guess is reasonable.

Also, hello to the mailing list :)

Cheers,

-AT


       reply	other threads:[~2009-06-08 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <80055d7c0906080553t41909b18j6c4a0f8fd119fa36@mail.gmail.com>
2009-06-08 12:55 ` Andrei Thorp [this message]
2009-06-08 13:03   ` Ben Walton

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=80055d7c0906080555h37e2b551i606e60dbdd5414f2@mail.gmail.com \
    --to=garoth@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