From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/2] avr: Removed errant control characters
Date: Sat, 28 May 2022 13:08:16 -0600 [thread overview]
Message-ID: <046a0f20-be04-5c92-973a-17b713534dda@gmail.com> (raw)
In-Reply-To: <20220401152029.63853-3-jholdsworth@nvidia.com>
On 4/1/2022 9:20 AM, Joel Holdsworth via Gcc-patches wrote:
> Signed-off-by: Joel Holdsworth <jholdsworth@nvidia.com>
> ---
> gcc/config/avr/avr-devices.cc | 2 --
> 1 file changed, 2 deletions(-)
These aren't really errant. There was a time when these form feeds were
actually encouraged and you'll find them all over the place in GCC.
I'd just assume remove them all at this point, but I think that would
need broader consensus.
jeff
prev parent reply other threads:[~2022-05-28 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 15:20 [PATCH 0/2] avr: Add support AVR-DA and DB series devices Joel Holdsworth
2022-04-01 15:20 ` [PATCH 1/2] avr: Added AVR-DA and DB MCU series Joel Holdsworth
2022-05-28 19:18 ` Jeff Law
2022-04-01 15:20 ` [PATCH 2/2] avr: Removed errant control characters Joel Holdsworth
2022-05-28 19:08 ` Jeff Law [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=046a0f20-be04-5c92-973a-17b713534dda@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@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).