From: Jan Beulich <jbeulich@suse.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Binutils <binutils@sourceware.org>,
Richard Earnshaw <rearnsha@arm.com>,
Marcus Shawcroft <marcus.shawcroft@arm.com>,
Srinath Parvathaneni <srinath.parvathaneni@arm.com>
Subject: Re: your patches enabling Arm64's SVE 2.1 extension
Date: Tue, 13 Feb 2024 12:39:58 +0100 [thread overview]
Message-ID: <4ecbe6ba-e3bb-4bf7-b737-dbab07c29dd6@suse.com> (raw)
In-Reply-To: <0f6f2ddf-0bac-4e9e-bca2-8b32060cf131@redhat.com>
On 13.02.2024 12:11, Nick Clifton wrote:
>> And no, I don't mean to strictly push for an eventual dot release. I
>> merely wanted to put up the question.
>
> That's fair. I did have another, slightly self-serving idea. How about,
> once these issues are resolved, you make a point release ? I have tried
> to document the process in the README-how-to-make-a-release file in the
> binutils directory and it would be great if there was someone besides
> myself who was able to make these releases. Plus, since I am probably
> the only person who has ever read the file, it would be good to get some
> feedback on its contents and accuracy...
>
> No pressure though. If you do not want to, or do not have the time, that
> is OK. I am just putting the idea out there.
Let me at least coarsely look over that file, one of these days, and then
come back. Time is the limiting factor, and after reading I may have an
understanding towards that (plus perhaps some questions up front).
Jan
next prev parent reply other threads:[~2024-02-13 11:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 8:00 Jan Beulich
2024-02-12 23:16 ` Srinath Parvathaneni
2024-02-13 7:24 ` Jan Beulich
2024-02-13 9:55 ` Nick Clifton
2024-02-13 10:48 ` Jan Beulich
2024-02-13 11:11 ` Nick Clifton
2024-02-13 11:39 ` Jan Beulich [this message]
2024-03-11 7:14 ` Jan Beulich
2024-02-15 11:21 ` Andrew Carlotti
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=4ecbe6ba-e3bb-4bf7-b737-dbab07c29dd6@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=marcus.shawcroft@arm.com \
--cc=nickc@redhat.com \
--cc=rearnsha@arm.com \
--cc=srinath.parvathaneni@arm.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).