gti-tac.lists.linuxfoundation.org archive mirror
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Carlos O'Donell <carlos@redhat.com>,
	Joseph Myers <joseph@codesourcery.com>
Cc: gti-tac@lists.linuxfoundation.org
Subject: Re: Planning the next GTI TAC meeting for February 2023?
Date: Wed, 8 Feb 2023 14:33:52 -0500	[thread overview]
Message-ID: <bf067980-f164-eb04-c70a-e1b80a336fac@gotplt.org> (raw)
In-Reply-To: <1344a6ae-15a4-f2c3-1abb-ced0caed9e59@redhat.com>

On 2023-02-07 12:34, Carlos O'Donell wrote:
> On 2/6/23 17:35, Joseph Myers wrote:
>> On Mon, 6 Feb 2023, Carlos O'Donell wrote:
>>
>>> With the binutils and glibc releases out of the way for January,
>>> I would like to schedule the next GTI TAC meeting and possibly
>>> setup a recurring monthly meeting to discuss progress.
>>>
>>> Suggestions for dates:
>>> Wednesday February 15th 11am EST / 4pm UTC
>>> Thursday February 16th 11am EST / 4pm UTC
>>> Friday February 17th 11am EST / 4pm UTC
>>
>> Unless next week's WG14 meeting processes comments much faster than
>> January's, I won't be able to do any of those.
>   
> Is the week after that week a better week?

I'm out the week after, but I can catch up on minutes, recordings, etc. 
and also help with any prep if needed.

Thanks,
Sid

      parent reply	other threads:[~2023-02-08 19:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 17:28 Planning the next GTI TAC meeting for February 2023? Carlos O'Donell
2023-02-06 22:35 ` Joseph Myers
2023-02-07 17:34   ` Carlos O'Donell
2023-02-07 18:35     ` Joseph Myers
2023-02-08 19:33     ` Siddhesh Poyarekar [this message]

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=bf067980-f164-eb04-c70a-e1b80a336fac@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=carlos@redhat.com \
    --cc=gti-tac@lists.linuxfoundation.org \
    --cc=joseph@codesourcery.com \
    /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).