public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: rebecca@bluestop.org
To: devel@edk2.groups.io, lersek@redhat.com, philmd@redhat.com,
	jian.j.wang@intel.com,
	"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>
Cc: "Ye, Ting" <ting.ye@intel.com>,
	Stephano Cetola <stephano.cetola@intel.com>
Subject: Re: [edk2-devel] [PATCH] CryptoPkg: add issetugid declaration to fix openssl build on FreeBSD
Date: Wed, 24 Apr 2019 13:36:48 -0600	[thread overview]
Message-ID: <e65b6c3d-3f9c-abcc-7c1d-4e63f797df74@bluestop.org> (raw)
In-Reply-To: <11affcc6-4611-ea2c-4c1b-1a1986369f45@redhat.com>

On 2019-04-24 13:17, Laszlo Ersek wrote:
>
> So I don't think there's anything to fix for package maintainers here.
> It seems that groups.io rewrites the sender address for Rebecca. I don't
> know why groups.io performs this rewrite, and why only for Rebecca.
>
> Stephano -- can you please ask groups.io why it keeps changing the From
> header on messages sent by "Rebecca Cran <rebecca@bluestop.org>"?



Trying again, now that I've disabled DKIM.


-- 
Rebecca Cran


  parent reply	other threads:[~2019-04-24 19:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-19 22:38 [PATCH] CryptoPkg: add issetugid declaration to fix openssl build on FreeBSD rebecca
2019-04-20 11:28 ` [edk2-devel] " Ard Biesheuvel
2019-04-20 11:30   ` Ard Biesheuvel
2019-04-20 17:18   ` rebecca
2019-04-22 13:46     ` Wang, Jian J
2019-04-24  9:25       ` Philippe Mathieu-Daudé
2019-04-24 19:17         ` Laszlo Ersek
2019-04-24 19:29           ` rebecca
2019-04-24 19:36           ` rebecca [this message]
2019-04-25  1:06             ` Wang, Jian J
2019-04-26 13:55           ` rebecca
2019-04-26 13:56             ` Andrew Fish
2019-04-26 14:07               ` rebecca
2019-04-26 20:19             ` Laszlo Ersek
2019-04-27  0:06               ` rebecca

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=e65b6c3d-3f9c-abcc-7c1d-4e63f797df74@bluestop.org \
    --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