public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tsukasa OI <research_trasio@irq.a4lg.com>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: Update mailing list address
Date: Thu, 1 Sep 2022 10:15:46 -0400	[thread overview]
Message-ID: <2a97ff52-3938-442a-fd44-6d991a21022e@simark.ca> (raw)
In-Reply-To: <ede57cbd-14c4-d44d-e669-0f103f24a371@irq.a4lg.com>

On 9/1/22 03:42, Tsukasa OI via Gdb-patches wrote:
> On 2022/08/31 4:00, Tom Tromey wrote:
>>>>>>> Tsukasa OI via Gdb-patches <gdb-patches@sourceware.org> writes:
>>
>>> The commit bf1102165389 "* MAINTAINERS: Perform some obvious fixups."
>>> back in 2009 changed the mailing list address gdb-patches@sources.redhat.com
>>> to gdb-patches@sourceware.org.
>>
>>> This commit does the same to sim/MAINTAINERS.
>>
>> Thanks.  I think this could go in under the "obvious" rule.
>>
>> Tom
>>
>
> Thanks for letting me know.
>
> But is this mean... can I just wait or do I need to resubmit as [OB
> PATCH]? (in general)
>
> Tsukasa

Hi,

Tom meant that the patch was OK to push, and that in his opinion you
could have pushed it directly, since it was obvious.  However, you might
not have push access, is that right?

In any case, I pushed the patch for you.

Simon

  reply	other threads:[~2022-09-01 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-27  2:12 Tsukasa OI
2022-08-30 19:00 ` Tom Tromey
2022-09-01  7:42   ` Tsukasa OI
2022-09-01 14:15     ` Simon Marchi [this message]
2022-09-02 11:18       ` Tsukasa OI

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=2a97ff52-3938-442a-fd44-6d991a21022e@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=research_trasio@irq.a4lg.com \
    --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).