Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: "Philipp Überbacher" <hollunder@lavabit.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] mailinglists in CC
Date: Thu, 19 Aug 2010 14:40:23 +0200	[thread overview]
Message-ID: <1282221544-sup-9759@eris> (raw)
In-Reply-To: <1282220819-sup-9512@theshire>

Excerpts from Erin Sheldon's message of 2010-08-19 14:27:04 +0200:
> Excerpts from Israel Herraiz's message of Thu Aug 19 07:58:29 -0400 2010:
> > Excerpts from Philipp's message of Thu Aug 19 06:52:56 -0400 2010:
> > > It's really annoying to send to single people instead of the list by
> > > accident.
> > 
> > It's really annoying to send a message to the list instead of to a
> > single person by accident.
> > 
> > In any case, mailing lists can set a Reply-To header, and I think Sup
> > will reply to the address included in that header. If it does not,
> > then I think that's a bug :-).
> > 
> > Cheers,
> > Israel
> 
> I partially agree.
> 
> I think we can take a lesson from gmail here:  A simple reply always
> replies to the sender. A group reply will include the list of course,
> and in that case you are responsible for trimming the recipients.  I've
> been caught by surprise when in 'sup a simple reply was sent to the list
> *instead* of the sender.  It is hard to predict when it will happen,
> because the Reply-To header is not ordinarily visible.
> 
> Erin Scott Sheldon

I'd like it the other way around, always reply to list and simply change
to 'sender' in the (at least for me) rare cases where it's not supposed
to go to the list.
-- 
Philipp

--
"Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu
und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

  reply	other threads:[~2010-08-19 12:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19 10:52 Philipp
2010-08-19 11:58 ` Israel Herraiz
2010-08-19 12:27   ` Erin Sheldon
2010-08-19 12:40     ` Philipp Überbacher [this message]
2010-08-19 13:07       ` Tero Tilus
2010-08-19 13:21         ` Helge Titlestad
2010-08-19 18:31           ` Tero Tilus
2010-08-19 14:26         ` Philipp Überbacher
2010-08-19 18:24           ` Tero Tilus
2010-08-19 19:19             ` Philipp Überbacher
2010-08-19 20:11             ` wagnerdm
2010-08-19 12:29   ` Philipp Überbacher
2010-08-19 12:49   ` Tero Tilus
2010-08-19 13:39     ` Israel Herraiz
2010-08-19 12:33 ` Tero Tilus
2010-08-19 12:58   ` Philipp Überbacher
2010-08-19 13:41     ` Israel Herraiz
2010-08-19 14:10       ` Philipp Überbacher

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=1282221544-sup-9759@eris \
    --to=hollunder@lavabit.com \
    --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