From: "Martin Liška" <mliska@suse.cz>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] changelog: Fix extra space after tab. fix extra spaces after tab
Date: Mon, 21 Nov 2022 10:14:26 +0100 [thread overview]
Message-ID: <32a455e0-d6ce-3d5e-ba32-e1c128c141f9@suse.cz> (raw)
In-Reply-To: <Y3tA4mfEbZEheoBX@tucnak>
On 11/21/22 10:12, Jakub Jelinek wrote:
> On Mon, Nov 21, 2022 at 09:19:24AM +0100, Martin Liška wrote:
>> The patch fixes ChangeLog format that is right now checked by server
>> hook.
>>
>> @Jakub: Can you please approve it? The change is mechanically done.
>
> LGTM, thanks.
> You even don't need to write ChangeLog entries for changes
> to ChangeLog files...
Correct, committed without the ChangeLog entries.
Martin
>
>> ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> contrib/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> fixincludes/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> gcc/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> gcc/ada/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> gcc/analyzer/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> gcc/c-family/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> gcc/cp/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> gcc/d/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> gcc/fortran/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> gcc/go/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> gcc/jit/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> gcc/lto/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> libdecnumber/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> libffi/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> libgcc/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> libgomp/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> libiberty/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> libitm/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> libobjc/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> libphobos/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> libquadmath/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> libsanitizer/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> libstdc++-v3/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>>
>> libvtv/ChangeLog: Fix extra space after tab.
>>
>> * ChangeLog: Fix extra space after tab.
>
> Jakub
>
next prev parent reply other threads:[~2022-11-21 9:14 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 [this message]
2022-11-21 9:23 ` Andreas Schwab
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=32a455e0-d6ce-3d5e-ba32-e1c128c141f9@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).