public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] sim: Update mailing list address
Date: Fri, 2 Sep 2022 20:18:05 +0900	[thread overview]
Message-ID: <dadcffe5-6431-dfbb-889a-b38be0a63845@irq.a4lg.com> (raw)
In-Reply-To: <2a97ff52-3938-442a-fd44-6d991a21022e@simark.ca>

On 2022/09/01 23:15, Simon Marchi wrote:
> 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
> 

Hello,

Thanks, I understand that.  Since I don't have a write access to
binutils-gdb.git, I needed someone to merge my change (I just started
talking about the Write After Approval access to Binutils [which I
mainly contribute] so getting write access to GDB will, at minimum, take
some time).  I appreciate that!

Thanks,
Tsukasa

      reply	other threads:[~2022-09-02 11:18 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
2022-09-02 11:18       ` Tsukasa OI [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=dadcffe5-6431-dfbb-889a-b38be0a63845@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --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).