From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [committed] libstdc++: Fix whitespace in license boilerplate
Date: Wed, 21 Apr 2021 14:03:30 +0200 [thread overview]
Message-ID: <20210421120330.GE1179226@tucnak> (raw)
In-Reply-To: <YIAUKNNMwjMet79L@redhat.com>
On Wed, Apr 21, 2021 at 01:01:44PM +0100, Jonathan Wakely via Gcc-patches wrote:
> libstdc++-v3/ChangeLog:
>
> * include/std/latch: Replace tab characters in license text.
> * include/std/semaphore: Likewise.
>
> Tested x86_64-linux. Committed to trunk.
>
> OK for gcc-11 too?
Yes.
> commit 88202c883c07da1c03dbb1ad440f1b70189c4399
> Author: Jonathan Wakely <jwakely@redhat.com>
> Date: Wed Apr 21 12:59:04 2021
>
> libstdc++: Fix whitespace in license boilerplate
>
> libstdc++-v3/ChangeLog:
>
> * include/std/latch: Replace tab characters in license text.
> * include/std/semaphore: Likewise.
Jakub
prev parent reply other threads:[~2021-04-21 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 12:01 Jonathan Wakely
2021-04-21 12:03 ` Jakub Jelinek [this message]
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=20210421120330.GE1179226@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--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).