From: "Martin Liška" <mliska@suse.cz>
To: Joseph Myers <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>,
Jason Merrill <jason@redhat.com>
Subject: Re: [PATCH] gcc-changelog: ignore one more revision
Date: Wed, 6 Apr 2022 09:12:17 +0200 [thread overview]
Message-ID: <034b3cb9-97b8-633c-d01a-e56c766b673f@suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2204042006500.326802@digraph.polyomino.org.uk>
On 4/4/22 22:07, Joseph Myers wrote:
> On Mon, 4 Apr 2022, Martin Liška wrote:
>
>> Ignore:
>>
>> Checking 86d8e0c0652ef5236a460b75c25e4f7093cc0651: FAILED
>> ERR: line should start with a tab: "This reverts commits r12-7804 and
>> r12-7929."
>> ERR: could not deduce ChangeLog file
>>
>> It seems Jason pushed the revision to origin/trunk where the checking script
>> is not run.
>
> I thought I'd fixed that (last August) by making the hooks-bin scripts
> handle master and trunk the same.
Well, I can't prove it, it's just a guess. Maybe Jason can answer the question?
Note the server hook should have rejected the revision.
Cheers,
Martin
prev parent reply other threads:[~2022-04-06 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 7:38 Martin Liška
2022-04-04 20:07 ` Joseph Myers
2022-04-06 7:12 ` Martin Liška [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=034b3cb9-97b8-633c-d01a-e56c766b673f@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=joseph@codesourcery.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).