From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Youling Tang <tangyouling@loongson.cn>
Cc: Richard Sandiford <richard.sandiford@arm.com>,
Andrew Burgess <aburgess@redhat.com>,
Lancelot SIX <lsix@lancelotsix.com>,
gdb-patches@sourceware.org
Subject: Re: [COMMITTED PATCH v2] gdb: mips: Fix the handling of complex type of function return value
Date: Mon, 11 Apr 2022 16:32:11 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2204111621240.9383@angie.orcam.me.uk> (raw)
In-Reply-To: <9e315c60-54e3-afdf-f28e-008854ffbe06@loongson.cn>
Hi Youling,
> > I cannot see you listed in MAINTAINERS, but your original change only had
> > a legally insignificant amount of changes, so I have now committed this
> > updated version. However for the sake of any future submissions you may
> > make can you please explain your current FSF copyright assignment status?
> I am working for Loongson Technology Corporation Limited.
> Loongson has signed the copyright assignment.
> Loongson GNU ANY is RT 1604586.
OK, this sounds good.
> Can I add to the MAINTAINERS list for the convenience of submitting code
> later?
You'll need to request repository write access first and have that
sponsored by a general maintainer. You'll be able to make such a request
once you have got one or a couple of good changes accepted. At that point
you'll add yourself to MAINTAINERS as your first change to the repository.
Maciej
next prev parent reply other threads:[~2022-04-11 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 4:48 [PATCH] " Youling Tang
2022-03-16 8:42 ` Lancelot SIX
2022-03-16 9:00 ` Youling Tang
2022-03-16 11:22 ` Andrew Burgess
2022-03-16 18:26 ` Maciej W. Rozycki
2022-03-17 7:01 ` Youling Tang
2022-04-06 22:46 ` [COMMITTED PATCH v2] " Maciej W. Rozycki
2022-04-07 2:19 ` Youling Tang
2022-04-11 15:32 ` Maciej W. Rozycki [this message]
2022-04-12 0:46 ` Youling Tang
2022-04-08 17:05 ` Richard Sandiford
2022-04-11 15:37 ` Maciej W. Rozycki
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=alpine.DEB.2.21.2204111621240.9383@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.com \
--cc=richard.sandiford@arm.com \
--cc=tangyouling@loongson.cn \
/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).