Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Marc Hartstein <marc.hartstein@alum.vassar.edu>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Help me getting started.
Date: Mon, 20 Dec 2010 13:24:27 -0500	[thread overview]
Message-ID: <1292869298-sup-8785@cabinet> (raw)
In-Reply-To: <4D0F5CA6.7070001@lophus.org>

Excerpts from Jonas H.'s message of Mon Dec 20 08:39:50 -0500 2010:
> [ Why doesn't this mailing list set the Reply-To header :'( ]

Because net standards require that mailing lists not override Reply-To
to set it to the mailing list. Reply-To is intended to always be the
proper address for a reply directly to the author. There are other
semi-official headers for mailing lists to use to instruct an MUA of the
correct address for mailing list replies. sup honors those and should
offer you the option of replying to the list.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-12-20 18:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-19 22:57 Jonas H.
2010-12-19 23:34 ` Ben Walton
2010-12-20  7:57 ` Tero Tilus
2010-12-20 13:39   ` Jonas H.
2010-12-20 18:24     ` Marc Hartstein [this message]
     [not found]   ` <4D0F5C5E.7030809@lophus.org>
2010-12-20 13:57     ` Tero Tilus
2010-12-23 10:17       ` Jonas H.
2010-12-30 13:14         ` Jonas H.
2010-12-30 15:31         ` Tero Tilus
2010-12-30 21:33           ` Tero Tilus
2010-12-30 23:09             ` Tero Tilus
2010-12-30 23:03         ` Tero Tilus
2010-12-30 23:37           ` Jonas H.
2010-12-31  0:45             ` Tero Tilus
2010-12-31 10:14               ` Jonas H.
2011-03-22 18:01                 ` Jonas H.
2010-12-20 13:41 ` Mark Alexander
2010-12-20 14:10   ` Shadowfirebird

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=1292869298-sup-8785@cabinet \
    --to=marc.hartstein@alum.vassar.edu \
    --cc=sup-talk@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox