From: Nelson Chu <nelson@rivosinc.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: binutils@sourceware.org
Subject: Re: Add the RISC-V bits to gas/NEWS
Date: Thu, 25 Aug 2022 16:20:27 +0800 [thread overview]
Message-ID: <CAPpQWtAiY=pMwXVhG3rjutwKj4zK5K4Vfh7F-V3v=Y4pOB-R1Q@mail.gmail.com> (raw)
In-Reply-To: <20220824201911.25495-1-palmer@rivosinc.com>
OK, these should mention all the past updates, including the 2.39, so committed.
Thanks
Nelson
On Thu, Aug 25, 2022 at 4:20 AM Palmer Dabbelt <palmer@rivosinc.com> wrote:
>
> This is somewhat embarassing, but looks like we've neglected to add NEWS
> entries since the one announcing our port. I've got through the history
> and tried to pull everything out, I think I got all the big stuff like
> new extensions.
>
>
prev parent reply other threads:[~2022-08-25 8:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 20:19 Palmer Dabbelt
2022-08-24 20:19 ` [PATCH 1/6] gas: NEWS: Add the RISC-V features for 2.31 Palmer Dabbelt
2022-08-24 20:19 ` Palmer Dabbelt
2022-08-24 20:19 ` [PATCH 2/6] gas: NEWS: Add the RISC-V features for 2.35 Palmer Dabbelt
2022-08-24 20:19 ` Palmer Dabbelt
2022-08-24 20:19 ` [PATCH 3/6] gas: NEWS: Add the RISC-V features for 2.36 Palmer Dabbelt
2022-08-24 20:19 ` Palmer Dabbelt
2022-08-24 20:19 ` [PATCH 4/6] gas: NEWS: Add the RISC-V features for 2.37 Palmer Dabbelt
2022-08-24 20:19 ` Palmer Dabbelt
2022-08-24 20:19 ` [PATCH 5/6] gas: NEWS: Add the RISC-V features for 2.38 Palmer Dabbelt
2022-08-24 20:19 ` Palmer Dabbelt
2022-08-24 20:19 ` [PATCH 6/6] gas: NEWS: Add the RISC-V features for 2.39 Palmer Dabbelt
2022-08-24 20:19 ` Palmer Dabbelt
2022-08-25 8:20 ` Nelson Chu [this message]
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='CAPpQWtAiY=pMwXVhG3rjutwKj4zK5K4Vfh7F-V3v=Y4pOB-R1Q@mail.gmail.com' \
--to=nelson@rivosinc.com \
--cc=binutils@sourceware.org \
--cc=palmer@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).