public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <quic_llindhol@quicinc.com>
To: Ard Biesheuvel <ardb@kernel.org>, <devel@edk2.groups.io>
Cc: Rebecca Cran <rebecca@bsdio.com>
Subject: Re: [edk2-devel] [PATCH RFC edk2-platforms 0/5] Phase out MPCore SEC drivers
Date: Tue, 30 Jul 2024 16:34:36 +0100	[thread overview]
Message-ID: <7d2f5c9a-3e80-4af4-b8d7-a0164800756d@quicinc.com> (raw)
In-Reply-To: <CAMj1kXGD_ptqBFWcV8hEpf_U-idboLtDXRSt0zAp8_1GuUD_Dg@mail.gmail.com>

On 2024-07-30 16:18, Ard Biesheuvel wrote:

>> Sure, that works for me.
>> I've released the stuck messages.
>>
>>> I probably need to subscribe ardb+git@google.com to the mailing list,
>>> which is the from" address when I send patches from my google dev
>>> machine.
>>
>> To be clear though, in the moderation system every single one of your
>> emails of the last few days are stuck with a different, obnoxious, email
>> address as the sender. It's not ardb+git@google.com.
>>
> 
> flex is an internal service to handle outgoing email, and I am using
> the internal git send-email helper built on top of that. I am not
> aware of any recent changes that would have provoked a change in
> behavior, and I see the same type of return paths on outgoing emails
> sent a year ago.

If that's true, then someone much more diligent than me has been 
manually releasing every patch you've sent, *or* something changed on 
the groups.io side recently.

/
     Leif



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120119): https://edk2.groups.io/g/devel/message/120119
Mute This Topic: https://groups.io/mt/107626521/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-07-30 15:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 12:22 [edk2-devel] [PATCH RFC edk2-platforms 0/5] Phase out MPCore SEC drivers Ard Biesheuvel via groups.io
2024-07-29 12:22 ` [edk2-devel] [PATCH RFC edk2-platforms 1/5] Platform AARCH64: Drop leftover references to deleted timer PCD Ard Biesheuvel via groups.io
2024-07-29 12:22 ` [edk2-devel] [PATCH RFC edk2-platforms 2/5] Platform AARCH64: Remove bogus references to MPCore stack Ard Biesheuvel via groups.io
2024-07-30 19:16   ` Sami Mujawar
2024-07-29 12:22 ` [edk2-devel] [PATCH RFC edk2-platforms 3/5] Platform/Ampere: Switch to unicore SEC implementation Ard Biesheuvel via groups.io
2024-07-31  8:21   ` Nhi Pham via groups.io
2024-07-29 12:22 ` [edk2-devel] [PATCH RFC edk2-platforms 4/5] Platform/Durian: " Ard Biesheuvel via groups.io
2024-07-29 12:22 ` [edk2-devel] [PATCH RFC edk2-platforms 5/5] Platform/HiSilicon/D0x: " Ard Biesheuvel via groups.io
2024-07-30 12:42 ` [edk2-devel] [PATCH RFC edk2-platforms 0/5] Phase out MPCore SEC drivers Leif Lindholm
2024-07-30 14:30   ` Rebecca Cran
2024-07-30 14:48     ` Leif Lindholm
2024-07-30 15:00       ` Ard Biesheuvel
2024-07-30 15:09         ` Leif Lindholm
2024-07-30 15:18           ` Ard Biesheuvel
2024-07-30 15:34             ` Leif Lindholm [this message]
2024-07-30 14:18 ` Rebecca Cran via groups.io
2024-07-30 15:48   ` Ard Biesheuvel

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=7d2f5c9a-3e80-4af4-b8d7-a0164800756d@quicinc.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