From: Ville Voutilainen <ville.voutilainen@gmail.com>
To: Ken Matsui <kmatsui@cs.washington.edu>
Cc: Jonathan Wakely <jwakely@redhat.com>,
gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: use __bool_constant instead of integral_constant
Date: Thu, 23 Mar 2023 12:46:26 +0200 [thread overview]
Message-ID: <CAFk2RUYFOXCNusO+zyUmBqCbHScVXdQ2Dswrw4LTwPNe6fWYUA@mail.gmail.com> (raw)
In-Reply-To: <CAML+3pW1CwxT2XpoUWh2uCtAujACmnYDor3-ARfAhZSoKLxomg@mail.gmail.com>
On Thu, 23 Mar 2023 at 12:18, Ken Matsui via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> Thank you so much for your review!
>
> This is my first time contributing to GCC, so I do not have a GCC
> copyright assignment. I googled those two ways, but I am still
> confused... Is it correct that the DCO sign-off has been getting more
> common recently? If so, I will put the sign-off into all my patches. I
> would prefer to choose the more common and lightweight way.
DCO sign-off is indeed more light-weight, and sure, it's becoming more common
since it's relatively new as an option.
next prev parent reply other threads:[~2023-03-23 10:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 2:04 Ken Matsui
2023-03-23 9:28 ` Jonathan Wakely
2023-03-23 10:17 ` Ken Matsui
2023-03-23 10:46 ` Ville Voutilainen [this message]
2023-03-23 10:53 ` Ken Matsui
2023-03-23 10:56 ` Ville Voutilainen
2023-03-23 11:00 ` Ken Matsui
2023-03-23 11:06 ` Ken Matsui
2023-04-08 1:02 ` PING: " Ken Matsui
2023-04-08 7:52 ` Jonathan Wakely
2023-04-08 21:08 ` Ken Matsui
2023-05-13 3:22 ` Ken Matsui
2023-05-17 15:53 ` Patrick Palka
2023-05-17 21:14 ` Ken Matsui
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=CAFk2RUYFOXCNusO+zyUmBqCbHScVXdQ2Dswrw4LTwPNe6fWYUA@mail.gmail.com \
--to=ville.voutilainen@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=kmatsui@cs.washington.edu \
--cc=libstdc++@gcc.gnu.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).