From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [OT] mailing list management
Date: Wed, 1 Jun 2005 12:46:36 +0200 [thread overview]
Message-ID: <20050601104636.GS2417@lug-owl.de> (raw)
In-Reply-To: <429D8E96.4010908@poczta.fm>
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
On Wed, 2005-06-01 12:31:50 +0200, Lukasz Stelmach <stlman@poczta.fm> wrote:
> Jan-Benedict Glaw napisał(a):
>
> >> I suggest
> >>(re)placing any Reply-To headers in incoming letters with Reply-To:
> >>linux-kernel@... before delivering them to subscribers.
> > >
> > This is considered harmful.
>
> Could you explain your point of view. I am subscribed to a list wher
> such a thing gets done and I haven't noticed any injures ;-)
http://www.unicom.com/pw/reply-to-harmful.html
> > Please just configure your email client
> > correctly.
> ^^^^^^^^^^^^
> That is?
>
> Well I might use "Reply to all" but then for example you would receive
> two copies of this email. One in your private inbox and the other in the
> list's box. Is this correct?
Reply-to-List is an option. For the LKML, it's even better to do a group
reply. This may allow the other party to answer in a fast manner, not
waiting for a delayed LKML email...
> I would even suggest placing real name in the reply to field next to
> list's address.
That's considered standard.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-01 10:46 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 10:13 [OT] mailing list management Lukasz Stelmach
2005-06-01 10:22 ` Jan-Benedict Glaw
2005-06-01 10:27 ` Christoph Hellwig
2005-06-01 10:34 ` Lukasz Stelmach
2005-06-01 10:43 ` Bernd Petrovitsch
2005-06-01 10:31 ` Lukasz Stelmach
2005-06-01 10:45 ` Bernd Petrovitsch
2005-06-01 11:02 ` Lukasz Stelmach
2005-06-01 17:37 ` Stefan Smietanowski
2005-06-02 9:45 ` Lukasz Stelmach
2005-06-01 10:46 ` Jan-Benedict Glaw [this message]
2005-06-01 10:49 ` Paulo Marques
2005-06-01 11:10 ` Lukasz Stelmach
2005-06-02 16:11 ` Keith Owens
2005-06-03 12:03 ` Lukasz Stelmach
2005-06-03 12:37 ` Jochen Striepe
2005-06-01 11:41 ` Paul Jakma
2005-06-01 12:44 ` Lukasz Stelmach
2005-06-01 13:01 ` Måns Rullgård
2005-06-02 9:50 ` Lukasz Stelmach
2005-06-02 12:34 ` Måns Rullgård
2005-06-03 11:42 ` Lukasz Stelmach
2005-06-03 11:46 ` Måns Rullgård
2005-06-01 13:25 ` Paul Jakma
2005-06-02 10:05 ` Lukasz Stelmach
2005-06-02 21:31 ` Michelle Konzack
2005-06-01 10:30 ` Måns Rullgård
2005-06-01 10:53 ` Lukasz Stelmach
2005-06-01 11:01 ` MadMike
2005-06-01 11:06 ` MadMike
2005-06-01 11:09 ` Matthias Andree
2005-06-01 11:14 ` Bernd Petrovitsch
2005-06-01 11:16 ` Jesper Juhl
2005-06-03 12:53 ` Matti Aarnio
[not found] <4ayEi-52j-23@gated-at.bofh.it>
[not found] ` <4ayNT-58e-27@gated-at.bofh.it>
[not found] ` <4az7m-5lG-31@gated-at.bofh.it>
2005-06-01 13:02 ` Bodo Eggert
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=20050601104636.GS2417@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.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 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.