From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
Jakub Jelinek <jakub@redhat.com>,
GCC Development <gcc@gcc.gnu.org>
Subject: Re: gccadmin hooks: make it a public git repo
Date: Wed, 13 Jan 2021 16:29:20 +0000 [thread overview]
Message-ID: <CAH6eHdSy7wCj26C-5=y3WiXGna-+-fjDv08AS5XzU3Wr-dio7A@mail.gmail.com> (raw)
In-Reply-To: <78b0e416-8766-f2a2-4214-3a1d36551420@suse.cz>
Makes sense to me.
On Thu, 7 Jan 2021 at 10:42, Martin Liška <mliska@suse.cz> wrote:
>
> Adding GCC ML.
>
> On 1/7/21 11:41 AM, Martin Liška wrote:
> > Hello.
> >
> > Time to time, I'm debugging git server hooks with Jakub and I'm always struggling
> > with miss of gccadmin hooks. I speak about the following repo:
> >
> > /home/gccadmin/hooks-bin:
> >
> > $ ls
> > commit_checker commit_email_formatter email-to-bugzilla-filtered email_to.py git_commit.py git_repository.py __pycache__ style_checker update_hook
> >
> > Can we please make it a public repo sitting here: https://gcc.gnu.org/git/ ?
> >
> > Second part of the server hooks are git-hooks which are public:
> > https://github.com/AdaCore/git-hooks/tree/master/hooks
> >
> > Thanks,
> > Martin
>
next prev parent reply other threads:[~2021-01-13 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d36a5ee2-d0aa-6fec-e330-20e796a93d9b@suse.cz>
2021-01-07 10:42 ` Martin Liška
2021-01-13 16:29 ` Jonathan Wakely [this message]
2021-01-13 17:00 ` Joseph Myers
2021-01-14 9:02 ` Martin Liška
2021-05-24 7:11 ` Martin Liška
2021-12-13 16:23 ` Martin Liška
2021-12-13 20:58 ` Joseph Myers
2021-12-14 15:40 ` Martin Liška
2021-12-14 16:14 ` Jonathan Wakely
2021-12-15 12:16 ` 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='CAH6eHdSy7wCj26C-5=y3WiXGna-+-fjDv08AS5XzU3Wr-dio7A@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.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).