From: Andreas Schwab <schwab@suse.de>
To: "Martin Liška" <mliska@suse.cz>
Cc: gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] changelog: Fix extra space after tab. fix extra spaces after tab
Date: Mon, 21 Nov 2022 10:23:42 +0100 [thread overview]
Message-ID: <mvm1qpwbqzl.fsf@suse.de> (raw)
In-Reply-To: <52b0c775-8950-7217-a861-6b1914f72fc7@suse.cz> ("Martin =?utf-8?Q?Li=C5=A1ka=22's?= message of "Mon, 21 Nov 2022 09:19:24 +0100")
On Nov 21 2022, Martin Liška wrote:
> diff --git a/ChangeLog b/ChangeLog
> index 9813596858d..0643a383872 100644
> --- a/ChangeLog
> +++ b/ChangeLog
> @@ -55,33 +55,33 @@
> 2022-11-09 Martin Liska <mliska@suse.cz>
>
> * doc/bsd.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/contrib.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/contribute.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/cppdiropts.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/cppenv.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/cppopts.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/cppwarnopts.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/funding.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/gnu.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/gnu_free_documentation_license.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/gpl-3.0.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/indices-and-tables.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/lgpl-2.1.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/md.rst:
> - Add trailing newline.
> + Add trailing newline.
>
> 2022-11-14 Martin Liska <mliska@suse.cz>
>
> @@ -188,33 +188,33 @@
> 2022-11-09 Martin Liska <mliska@suse.cz>
>
> * doc/bsd.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/contrib.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/contribute.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/cppdiropts.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/cppenv.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/cppopts.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/cppwarnopts.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/funding.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/gnu.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/gnu_free_documentation_license.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/gpl-3.0.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/indices-and-tables.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/lgpl-2.1.rst:
> - Add trailing newline.
> + Add trailing newline.
> * doc/md.rst:
> - Add trailing newline.
> + Add trailing newline.
That should be refilled, every file entry on one line.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2022-11-21 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 8:19 Martin Liška
2022-11-21 9:12 ` Jakub Jelinek
2022-11-21 9:14 ` Martin Liška
2022-11-21 9:23 ` Andreas Schwab [this message]
2022-11-21 9:31 ` Martin Liška
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=mvm1qpwbqzl.fsf@suse.de \
--to=schwab@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mliska@suse.cz \
/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).