From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, James.Bottomley@HansenPartnership.com
Cc: ekhoruzhenko@absolute.com,
Paulo Henrique Lacerda de Amorim <phlamorim@riseup.net>
Subject: Re: [edk2-devel] Interpretation of specification
Date: Fri, 10 Jan 2020 11:55:03 +0100 [thread overview]
Message-ID: <f7735c35-b2ac-e337-474d-b2bc8a77fdf1@redhat.com> (raw)
In-Reply-To: <1578590422.3526.6.camel@HansenPartnership.com>
On 01/09/20 18:20, James Bottomley wrote:
> On Thu, 2020-01-09 at 18:17 +0100, Laszlo Ersek wrote:
>> Hello James,
>>
>> On 01/08/20 20:13, James Bottomley wrote:
>>> On Wed, 2020-01-08 at 12:24 +0100, Laszlo Ersek wrote:
>>>> I don't know where sbsigntools development occurs (mailing list,
>>>> bug
>>>> tracker, ...). For now, I'm CC'ing James. (The git repo lives in
>>>> his
>>>> space on <git.kernel.org>.)
>>>
>>> Heh, that's a sore point: since Jeremy Kerr left ubuntu, no-one
>>> except
>>> me has been maintaining it; Jeremy owns the original tree on the
>>> Ubuntu
>>> servers but can't update it any more.
>>>
>>> I use groups.io for the openssl_tpm2_engine development list, so I
>>> suppose I can set one up for sbsigntools ... OK, done. If you want
>>> to
>>> you can package the above up as a patch and send it there and I'll
>>> apply it.
>>
>> I've now posted:
>>
>> [PATCH] sbvarsign: fix
>> "EFI_VARIABLE_AUTHENTICATION_2.TimeStamp.Year" assignment
>> Message-Id: <20200109171302.28782-1-lersek@redhat.com>
>>
>> to <sbsigntools@groups.io>.
>>
>> I didn't (and most likely, won't) subscribe to that list, so please
>> whitelist this individual posting of mine, on the <https://sbsigntool
>> s.groups.io> admin interface.
>
> Heh, trying to dust off the groups.io setup memories as we speak. I
> can't allow fully unmoderated postings, unfortunately.
Right, that's my understanding too -- fully open lists are not supported
on groups.io (and at least in the edk2 community, most participants
don't like fully open posting -- I happen to be a fan of open posting,
FWIW). Worse, for non-subscribers, the best that groups.io offers is
white-listing per *message*, and not per *sender*.
> I also think
> the group rejected this out of hand because it's not in the moderation
> queue, but I think I've found the flag that holds non-member posts for
> moderation and thus allows them to be posted instead of rejected.
Ugh, I didn't know that just holding messages for moderation took a
separate setting!
Thanks!
Laszlo
next prev parent reply other threads:[~2020-01-10 10:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 17:12 Interpretation of specification phlamorim
2019-10-24 12:33 ` [edk2-devel] " Laszlo Ersek
2019-11-15 18:51 ` phlamorim
2019-11-15 21:32 ` Laszlo Ersek
2019-11-23 4:59 ` Eugene Khoruzhenko
2019-11-23 13:08 ` Paulo Henrique Lacerda de Amorim
2019-11-26 6:08 ` Eugene Khoruzhenko
2019-11-26 15:22 ` Paulo Henrique Lacerda de Amorim
2020-01-03 19:52 ` Eugene Khoruzhenko
2020-01-04 17:17 ` Paulo Henrique Lacerda de Amorim
2020-01-07 18:13 ` Eugene Khoruzhenko
2020-01-08 11:24 ` Laszlo Ersek
2020-01-08 19:13 ` James Bottomley
2020-01-09 17:17 ` Laszlo Ersek
2020-01-09 17:20 ` James Bottomley
2020-01-10 10:55 ` Laszlo Ersek [this message]
2020-01-10 16:04 ` James Bottomley
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=f7735c35-b2ac-e337-474d-b2bc8a77fdf1@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