From: Joseph Myers <joseph@codesourcery.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] gcc-changelog: ignore one more revision
Date: Mon, 4 Apr 2022 20:07:42 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2204042006500.326802@digraph.polyomino.org.uk> (raw)
In-Reply-To: <dadf1eb8-2ef1-631f-fa6e-630372c2566a@suse.cz>
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.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-04-04 20:07 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 [this message]
2022-04-06 7:12 ` 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=alpine.DEB.2.22.394.2204042006500.326802@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--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).