public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Carsey, Jaben" <jaben.carsey@intel.com>,
	Leif Lindholm <leif.lindholm@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Gao, Liming" <liming.gao@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH] BaseTools: Fix build failure when specifying multiple BUILDTARGET
Date: Wed, 6 Feb 2019 17:16:54 +0100	[thread overview]
Message-ID: <c4308d8d-bee7-60f7-f296-26a939b80e99@redhat.com> (raw)
In-Reply-To: <CB6E33457884FA40993F35157061515CBCB696E4@ORSMSX153.amr.corp.intel.com>

On 02/05/19 22:20, Carsey, Jaben wrote:
> Laszlo,
> 
> not sure which Andrew you wanted, but he didn’t get added so far as I can tell.

He did, it's just the mailman2 list software pulling tricks on us again.

The default setting for list subscribers is to eliminate duplicates.
That is, if you are subscribed to the list, and someone send an email to
both the list and you personally, then mailman2 will see that you are
already CC'd on the original, so it will not deliver a 2nd copy to you.
The trick is that mailman2 will also strip your address from the copy
that it delivers to *other* list subscribers. Those other subscribers
won't be able to tell whether the original sender CC'd you or not.

If you manually invert this setting at
<https://lists.01.org/mailman/options/edk2-devel> (it's called "enable
duplicates" or something similar), then you will get two copies of the
original email, one directly, and another from the list. (This is
generally the more useful setting, because you can file the reflected
copy in your list folder, and keep the direct email in your inbox.) The
trick is that in this case mailman2 will *not* strip your address from
the copy that it reflects to the other subscribers.

So now you can tell that Mike has duplicates enabled, and Andrew has
them disabled. :)

>> I suggest we push the (upcoming v2) patch tomorrow.
> 
> Agreed.  I can push if desired, once final version is complete.

Thanks for that!
Laszlo


  reply	other threads:[~2019-02-06 16:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05  1:23 [PATCH] BaseTools: Fix build failure when specifying multiple BUILDTARGET Philippe Mathieu-Daudé
2019-02-05  9:03 ` Laszlo Ersek
2019-02-05 11:47   ` Leif Lindholm
2019-02-05 12:04     ` Laszlo Ersek
2019-02-05 21:20       ` Carsey, Jaben
2019-02-06 16:16         ` Laszlo Ersek [this message]
2019-02-05 12:02   ` Philippe Mathieu-Daudé
2019-02-05 12:06     ` Laszlo Ersek

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-list 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=c4308d8d-bee7-60f7-f296-26a939b80e99@redhat.com \
    --to=devel@edk2.groups.io \
    /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