[PATCH] MAINTAINERS: move Jim Wilson to Past Maintainers

[Palmer Dabbelt]

On Fri, 29 Aug 2025 08:49:54 PDT (-0700), wilson@tuliptree.org wrote:
> On Tue, 2025-08-26 at 02:49 +0100, Sam James wrote:
>> Jan Beulich <jbeulich@suse.com> writes:
>> 
>> > ..., effectively yielding IA-64 maintainer-less, as per his
>> > request:
>> > https://sourceware.org/pipermail/binutils/2025-August/143393.html
>> > https://sourceware.org/pipermail/binutils/2025-August/143491.html
>> > Jim - thanks much for your past work.
>> > 
>> 
>> Jim, you're still listed as RISC-V maintainer. Do you wish to retain
>> that status? (If so, not sure if we should move you out of "Past
>> Maintainers").
>> 
>> You're also listed as maintainer for a few components in GCC. Do
>> those
>> need updating too?
>
> I still care about RISC-V unlike IA-64.  I also still read some of the
> RISC-V mailing lists.  So I can be a backup maintainer for RISC-V if
> that is useful.  I can not be the primary maintainer.  That should be
> Nelson Chu, at least last time I checked.  Andrew Waterman wrote the

Ya, it's Nelson still.  I pretty much only jump in when Nelson pokes me 
about something he wants me to look at.

> original port, but I don't think that he has contributed in a long time
> and he is probably not following the binutils mailing list.  Palmer
> Dabbelt mostly works on other projects but is a reasonable backup to
> Nelson, and then I can back up Palmer if necessary.
>
> As for GCC, I should not be primary maintainer for anything, but I
> don't think that I am.  I did resign as GCC IA-64 maintainer a few
> years ago.  I just forgot to do that for Binutils at the same time.
>
> To better state my current status, I retired and decided to take some
> time off from GNU toolchain work.  I figured when I started getting
> bored I would return.  But that was almost 4 years ago, and I haven't
> gotten bored enough yet.  I'm still thinking I will return at some
> point, but I have no idea when.

OK, you're always welcome back ;)