From: Simon Marchi <simark@simark.ca>
To: Nick Clifton <nickc@redhat.com>,
andreas@rammhold.de, gdb-patches@sourceware.org,
Binutils <binutils@sourceware.org>
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH v2] Use sha256 for hashes in the release process
Date: Tue, 27 Oct 2020 12:52:34 -0400 [thread overview]
Message-ID: <b82f821d-0d0e-e27d-6a32-f01168cdad0c@simark.ca> (raw)
In-Reply-To: <5825aff7-e1ed-d115-4d20-55b18d277706@redhat.com>
On 2020-10-27 12:50 p.m., Nick Clifton wrote:
> Hi Simon,
>
>> Again, this must be sent to the binutils mailing list as well, I added
>> it.
>>
>> Here's the link to the patch:
>>
>> https://sourceware.org/pipermail/gdb-patches/2020-October/172866.html
>
> I am all for this. Approved from a binutils point of view.
>
> Cheers
> Nick
Thanks Nick. CC-ing Joel, hopefully, he can take a quick look and approve it.
Simon
next prev parent reply other threads:[~2020-10-27 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 3:03 andreas
2020-10-26 14:12 ` Simon Marchi
2020-10-27 16:50 ` Nick Clifton via Gdb-patches
2020-10-27 16:52 ` Simon Marchi [this message]
2020-10-28 10:41 ` Joel Brobecker
2020-10-28 14:36 ` Simon Marchi
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=b82f821d-0d0e-e27d-6a32-f01168cdad0c@simark.ca \
--to=simark@simark.ca \
--cc=andreas@rammhold.de \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=nickc@redhat.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