public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ken Matsui <kmatsui@cs.washington.edu>
To: Ville Voutilainen <ville.voutilainen@gmail.com>
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 04:00:40 -0700	[thread overview]
Message-ID: <CAML+3pXgiJ93E=16mDnhMBaYy1RETKkqw9G8YA+BNFMxuG8eng@mail.gmail.com> (raw)
In-Reply-To: <CAFk2RUZxx8m7T_Sa4KGThN3oBGPb=XPODik=tUbVSj0QWcOkVg@mail.gmail.com>

On Thu, Mar 23, 2023 at 3:56 AM Ville Voutilainen
<ville.voutilainen@gmail.com> wrote:
>
> On Thu, 23 Mar 2023 at 12:53, Ken Matsui <kmatsui@cs.washington.edu> wrote:
>
> > > DCO sign-off is indeed more light-weight, and sure, it's becoming more common
> > > since it's relatively new as an option.
> >
> > Thank you!
> >
> > To add a DCO sign-off, do I need to bump up the subject line to [PATCH v2]?
>
> No. The format of the subject for patch submission emails is not that strict. :)

I see. I will update this patch. Thank you so much for your support!

Sincerely,
Ken Matsui

  reply	other threads:[~2023-03-23 11:00 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
2023-03-23 10:53       ` Ken Matsui
2023-03-23 10:56         ` Ville Voutilainen
2023-03-23 11:00           ` Ken Matsui [this message]
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='CAML+3pXgiJ93E=16mDnhMBaYy1RETKkqw9G8YA+BNFMxuG8eng@mail.gmail.com' \
    --to=kmatsui@cs.washington.edu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=ville.voutilainen@gmail.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).