public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
	Mark Wielaard <mark@klomp.org>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: Updating mailman settings to avoid From rewriting
Date: Sat, 14 Oct 2023 16:26:08 -0400	[thread overview]
Message-ID: <2be18895-f396-4fca-b78b-016c33726f70@simark.ca> (raw)
In-Reply-To: <87il79p4t1.fsf@linaro.org>

On 10/14/23 12:06, Thiago Jung Bauermann wrote:
> 
> Mark Wielaard <mark@klomp.org> writes:
> 
>> On Tue, Oct 10, 2023 at 01:00:37PM -0600, Tom Tromey wrote:
>>>>> We still need admins/moderators for these two lists.
>>>
>>> Thiago> I'm not a maintainer or anything in GDB nor GNU, but if that isn't a
>>> Thiago> prerequisite and if other people are OK with it I'd be happy to be list
>>> Thiago> admin for gdb-patches.
>>>
>>> I think this would be fine.  Thank you for volunteering.
>>
>> Thiago is now admin/moderator of the gdb and gdb-patches mailinglists.
>> Please reach out to the list or overseers@sourceware.org if you feel
>> you need an extra person helping out.
> 
> Thanks Mark, I'm set up now.
> 
> If anyone needs help with anything regarding the mailing lists or has
> any suggestion, feel free to contact me either in public or in private.

Thanks a lot Thiago for stepping up for this.

Simon

      reply	other threads:[~2023-10-14 20:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02 22:12 Mark Wielaard
2023-10-07  0:14 ` Mark Wielaard
2023-10-07  3:55   ` Thiago Jung Bauermann
2023-10-07 12:20     ` Benson Muite
2023-10-08 21:12       ` Mark Wielaard
2023-10-10 19:00     ` Tom Tromey
2023-10-14  1:11       ` Mark Wielaard
2023-10-14 16:06         ` Thiago Jung Bauermann
2023-10-14 20:26           ` Simon Marchi [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=2be18895-f396-4fca-b78b-016c33726f70@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=mark@klomp.org \
    --cc=thiago.bauermann@linaro.org \
    --cc=tom@tromey.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 read-only IMAP folder(s) and NNTP newsgroup(s).