[PATCH] sim: Update mailing list address

[PATCH] sim: Update mailing list address

[Tsukasa OI]

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.

sim/ChangeLog:

	* MAINTAINERS: Update mailing list address.
---
 sim/MAINTAINERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sim/MAINTAINERS b/sim/MAINTAINERS
index 2d9c0757160..ac79a6db544 100644
--- a/sim/MAINTAINERS
+++ b/sim/MAINTAINERS
@@ -5,7 +5,7 @@ gdb/MAINTAINERS for general information about maintaining these files.
 
 If you are considering contributing a patch, please see the file
 gdb/CONTRIBUTE.  Patches to these files should be posted to:
-gdb-patches@sources.redhat.com 
+gdb-patches@sourceware.org
 
         Global Maintainers
 

base-commit: 46e59b72f21029f2a863e3828cec76a03283b49d
-- 
2.34.1

Re: [PATCH] sim: Update mailing list address

[Tom Tromey]

>>>>> 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

Re: [PATCH] sim: Update mailing list address

[Tsukasa OI]

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

Re: [PATCH] sim: Update mailing list address

[Simon Marchi]

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

Re: [PATCH] sim: Update mailing list address

[Tsukasa OI]

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