ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Laura Abbott <laura@labbott.name>
To: Geert Uytterhoeven <geert@linux-m68k.org>, Dave Hansen <dave@sr71.net>
Cc: "tab-elections@lists.linuxfoundation.org"
	<tab-elections@lists.linuxfoundation.org>,
	ksummit@lists.linux.dev,
	"tech-board-discuss@lists.linuxfoundation.org"
	<tech-board-discuss@lists.linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Tech-board-discuss] IMPORTANT: CIVS opt-in for Technical Advisory Board voting
Date: Mon, 20 Sep 2021 12:18:09 -0400	[thread overview]
Message-ID: <bf22702e-01b2-214a-1650-da9e4ec3c2be@labbott.name> (raw)
In-Reply-To: <CAMuHMdVtHDQ2f0VKAdQFQV9dZJ5uFGD9yHvNviQ_k7AEfhN77w@mail.gmail.com>

On 9/20/21 12:03, Geert Uytterhoeven wrote:
> On Mon, Sep 20, 2021 at 5:48 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>> On Mon, Sep 20, 2021 at 5:37 PM Dave Hansen <dave@sr71.net> wrote:
>>> My @linux.intel.com account is the most common one from the git logs.  I
>>> have only received one TAB-related email there:
>>>
>>>          Subject: Upcoming Technical Advisory Board election -- look for
>>>                   your ballot
>>>
>>> However, I never actually received a ballot at that email, presumably
>>> because of this CIVS opt-in issue.
>>>
>>> Was this just me?  Or would it be appropriate to send these opt-in
>>> instructions to all of those that should have received a ballot instead
>>> of just sending to the mailing lists?
>>
>> I did the CIVS opt-in, and entered the confirmation number.
>> Still, unlike Vlastimil, I saw no way to vote?
>> Just retried the opt-in, "already opted-in".
> 
> If you use multiple email addresses, make sure to opt-in using the exact
> same one on which you received the original email from Laura.
> Then there will be a link to the actual poll after entering the confirmation
> code.
> 
> Gr{oetje,eeting}s,
> 
>                          Geert
> 

Yes that is correct. We attempted to consolidate e-mail addresses if you
contribute under multiple ones. This is a pain point we will need to fix
next year.

Thanks,
Laura

  reply	other threads:[~2021-09-20 16:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20 13:57 IMPORTANT: CIVS opt-in for Technical Advisory Board voting Laura Abbott
2021-09-20 15:16 ` Vlastimil Babka
2021-09-20 15:36   ` Jan Kara
2021-09-20 15:30 ` Dave Hansen
2021-09-20 15:48   ` Geert Uytterhoeven
2021-09-20 16:03     ` Geert Uytterhoeven
2021-09-20 16:18       ` Laura Abbott [this message]
2021-09-20 16:23         ` [Tech-board-discuss] " Mark Brown
2021-09-20 16:30           ` Laura Abbott
2021-09-20 16:48             ` Mark Brown
2021-09-20 16:53               ` Laura Abbott
2021-09-20 16:57                 ` Mark Brown
2021-09-20 17:10                   ` Laura Abbott
2021-09-20 17:12                     ` Mark Brown
2021-09-20 17:11                   ` Geert Uytterhoeven
2021-09-20 17:15                     ` Mark Brown
2021-09-20 16:15   ` [Tab-elections] " Laura Abbott

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=bf22702e-01b2-214a-1650-da9e4ec3c2be@labbott.name \
    --to=laura@labbott.name \
    --cc=dave@sr71.net \
    --cc=geert@linux-m68k.org \
    --cc=ksummit@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tab-elections@lists.linuxfoundation.org \
    --cc=tech-board-discuss@lists.linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).