From: Patrick Ohly <patrick.ohly@intel.com>
To: openembedded-devel@lists.openembedded.org,
Michael Halstead <mhalstead@linuxfoundation.org>
Subject: Reply-To (was: Re: [meta-oe][PATCH 1/4] lvm2: remove unbuildable 2.02.138)
Date: Thu, 09 Feb 2017 20:21:29 +0100 [thread overview]
Message-ID: <1486668089.13854.119.camel@intel.com> (raw)
In-Reply-To: <CAMKF1sqH1XGcG47CGp-CcgE5EYJ2_JE6wBw9V3=XDJ9-=LUHsw@mail.gmail.com>
On Thu, 2017-02-09 at 09:17 -0800, Khem Raj wrote:
> On Thu, Feb 9, 2017 at 9:11 AM, Patrick Ohly <patrick.ohly@intel.com> wrote:
> > BTW, do all mails from openembedded-devel have Reply-To:
> > <openembedded-devel@lists.openembedded.org> set? openembedded-core
> > doesn't seem to have that.
>
> yeah I guess reply-all will send to all but I never tried that
Depends on the client, but typically "Reply-To" sends a very strong
message that the only intended reply is to the given address. For
example, I always do group-reply in Evolution, and for this list it only
picks the list address, as it should.
See
http://www.unicom.com/pw/reply-to-harmful.html
Does anyone remember why the list is set up this way?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-02-09 19:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 9:37 [meta-oe][PATCH 0/4] native cryptsetup and fuse Patrick Ohly
2017-02-08 9:37 ` [meta-oe][PATCH 1/4] lvm2: remove unbuildable 2.02.138 Patrick Ohly
2017-02-08 20:21 ` Khem Raj
2017-02-09 17:11 ` Patrick Ohly
2017-02-09 17:17 ` Khem Raj
2017-02-09 19:21 ` Patrick Ohly [this message]
2017-02-10 23:15 ` Martin Jansa
2017-02-13 7:23 ` Patrick Ohly
2017-02-08 9:37 ` [meta-oe][PATCH 2/4] fuse: support native compilation Patrick Ohly
2017-02-08 9:37 ` [meta-oe][PATCH 3/4] lvm2: enable " Patrick Ohly
2017-02-08 9:37 ` [meta-oe][PATCH 4/4] cryptsetup: " Patrick Ohly
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=1486668089.13854.119.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=mhalstead@linuxfoundation.org \
--cc=openembedded-devel@lists.openembedded.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.