From: Javier Mora <cousteaulecommandant@gmail.com>
To: Nelson Chu <nelson@rivosinc.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH v2] gas/doc: RISC-V: Fix Type U instruction
Date: Thu, 30 May 2024 17:35:39 +0200 [thread overview]
Message-ID: <CAH1-q0ia0rM9qenEk5zcUCfZqfaypKwLPE5wJbj4aGKswMuRUQ@mail.gmail.com> (raw)
In-Reply-To: <CAPpQWtBCJdr60-VxiNQxE4HabKE+HxKpsHCnCpu4tKYimYL0eg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
Do I need to do that now (for this patch), or only for future patches?
El jue, 30 may 2024, 3:15, Nelson Chu <nelson@rivosinc.com> escribió:
>
>
> On Tue, May 28, 2024 at 11:52 AM Nelson Chu <nelson@rivosinc.com> wrote:
>
>> Hi,
>>
>> This fix looks good and reasonable. Besides, since it looks quite an
>> institute and a small document fix, I think it should be fine to commit for
>> now.
>>
>> If you are interesting in further contributions, then it would be great
>> and convenient if you have the GNU copyright assignment. Please see the
>> details as follow,
>>
>> https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=tree;f=doc/Copyright
>>
>> You can fill one of them (probably, seem like all three look the same ),
>> and then send it to assign@gnu.org, to get your copyright assignment.
>>
>
> Or you can add the "Signed-off-by: your name <your email>" in the commit
> message every time, that also work.
> https://sourceware.org/pipermail/binutils/2022-October/123680.html
>
next prev parent reply other threads:[~2024-05-30 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 18:45 [PATCH] " Javier Mora
2024-05-26 17:44 ` [PATCH v2] " Javier Mora
2024-05-28 3:52 ` Nelson Chu
2024-05-30 1:15 ` Nelson Chu
2024-05-30 15:35 ` Javier Mora [this message]
2024-05-31 8:10 ` Nelson Chu
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=CAH1-q0ia0rM9qenEk5zcUCfZqfaypKwLPE5wJbj4aGKswMuRUQ@mail.gmail.com \
--to=cousteaulecommandant@gmail.com \
--cc=binutils@sourceware.org \
--cc=nelson@rivosinc.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).