From: Nick Clifton <nickc@redhat.com>
To: Binutils <binutils@sourceware.org>
Subject: Announcement: DCO signed contributions are now accepted
Date: Tue, 18 Oct 2022 17:27:01 +0100 [thread overview]
Message-ID: <666c001a-2e88-a68d-d383-8fc0cc9a3a48@redhat.com> (raw)
Hi Guys,
I am pleased to announce that the GNU Binutils project will now
accept contributes signed with a Developer's Certificate of Origin:
https://gcc.gnu.org/dco.html
Whilst there are concerns about DCOs, they are now widely adopted
within the GNU Toolchain community as a whole, and there is no reason
why the binutils should be the odd one out.
I will be updating the text in the binutils/MAINTAINERS file to
reflect this change.
Cheers
Nick
reply other threads:[~2022-10-18 16:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=666c001a-2e88-a68d-d383-8fc0cc9a3a48@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
/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).