From: "Martin Liška" <mliska@suse.cz>
To: Carlos O'Donell <carlos@redhat.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Jeff Law <jeffreyalaw@gmail.com>
Cc: gti-tac@lists.linuxfoundation.org
Subject: Re: GTI TAC Meeting Notes 2023-06-08
Date: Fri, 10 Mar 2023 09:01:30 +0100 [thread overview]
Message-ID: <a3b10266-2bf7-44da-249f-7d01e36ac253@suse.cz> (raw)
In-Reply-To: <83b7663a-114d-6fcd-6a62-ed3e79ba65bb@redhat.com>
On 3/10/23 05:50, Carlos O'Donell wrote:
> The gcc project itself has ~6k lines of python in the git commit
> hooks and part of that handles "message" customization.
Hi.
Do you mean the copy of contrib/gcc-changelog where we verify the ChangeLog format?
Note it's just of copy of what we have in the main repo:
https://gcc.gnu.org/git/?p=gcc.git;a=tree;f=contrib/gcc-changelog;h=1978dc6e4f6572e88b27898a9abe849d7ccdb883;hb=HEAD
Cheers,
Martin
prev parent reply other threads:[~2023-03-10 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 16:44 GTI TAC Meeting Notes 2023-06-08 Carlos O'Donell
2023-03-08 19:29 ` Konstantin Ryabitsev
2023-03-10 4:50 ` Carlos O'Donell
2023-03-10 8:01 ` 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=a3b10266-2bf7-44da-249f-7d01e36ac253@suse.cz \
--to=mliska@suse.cz \
--cc=carlos@redhat.com \
--cc=gti-tac@lists.linuxfoundation.org \
--cc=jeffreyalaw@gmail.com \
--cc=konstantin@linuxfoundation.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).