From: Joel Brobecker <brobecker@adacore.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Modify gdb.base/charset.c to fix some issues
Date: Sat, 8 Jan 2022 12:29:24 +0400 [thread overview]
Message-ID: <YdlLZHxJj0qLJaaZ@adacore.com> (raw)
In-Reply-To: <741dfadd-bebf-d8f7-5e7b-897b32f489de@loongson.cn>
> > > Tiezhu Yang (2):
> > > gdb: testsuite: fix failed testcases in gdb.base/charset.exp
> > > gdb: testsuite: fix wrong comment in gdb.base/charset.c
> >
> > Thanks for those patches. They look good to me.
> >
> > Do you have a copyright assignment on file for GDB? I searched
> > the FSF records, and couldn't find your name. If not, we can
> > take your changes under the "tiny patch" rule.
>
> Thank you very much for your reply.
>
> I am working for Loongson Technology Corporation Limited.
> Loongson has signed the copyright assignment.
> Loongson GNU ANY is RT 1604586.
Great. Do you have write access to the repository? It's looking
like you are contributing more to the project, so it would make
sense to me if you were allowed to push to the repository though
our "Write After Approval" procedure.
--
Joel
next prev parent reply other threads:[~2022-01-08 8:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-25 4:03 Tiezhu Yang
2021-12-25 4:03 ` [PATCH 1/2] gdb: testsuite: fix failed testcases in gdb.base/charset.exp Tiezhu Yang
2022-01-10 2:42 ` Simon Marchi
2022-01-10 3:23 ` Tiezhu Yang
2022-01-12 4:28 ` Simon Marchi
2022-01-12 11:31 ` Tiezhu Yang
2022-01-12 17:14 ` Simon Marchi
2022-01-13 1:22 ` Tiezhu Yang
2022-01-13 1:26 ` Simon Marchi
2022-01-13 3:39 ` Tiezhu Yang
2022-01-13 15:14 ` Simon Marchi
2021-12-25 4:03 ` [PATCH 2/2] gdb: testsuite: fix wrong comment in gdb.base/charset.c Tiezhu Yang
2021-12-29 4:25 ` [PATCH 0/2] Modify gdb.base/charset.c to fix some issues Joel Brobecker
2021-12-30 3:10 ` Tiezhu Yang
2022-01-08 8:29 ` Joel Brobecker [this message]
2022-01-09 5:22 ` Tiezhu Yang
2022-01-09 8:02 ` Joel Brobecker
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=YdlLZHxJj0qLJaaZ@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=yangtiezhu@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).