From: Joseph Myers <joseph@codesourcery.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Jason Merrill <jason@redhat.com>, <gcc@gcc.gnu.org>,
<brobecker@adacore.com>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
Daniel Berlin <dberlin@dberlin.org>
Subject: Re: GCC Git hooks
Date: Sun, 15 Sep 2019 12:07:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1909151205100.19246@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.LSU.2.21.1909151143420.8294@anthias.pfeifer.com>
On Sun, 15 Sep 2019, Gerald Pfeifer wrote:
> Let me know how I can help, and I will do my best. (Even if I'll be
> offline most of the next three weeks, I can get online most days and
> spend some time.)
Apart from general review of the test conversion / conversion and hook
scripts, which everyone can do, I think the main thing would be to advise
on what needs to happen to avoid breaking the www.gnu.org copy of the site
and your HTML validation system for commits.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-09-15 12:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-14 20:53 Jason Merrill
2019-09-15 1:54 ` Joseph Myers
2019-09-15 3:50 ` Gerald Pfeifer
2019-09-15 12:07 ` Joseph Myers [this message]
2019-09-15 16:16 ` Gerald Pfeifer
2019-09-16 15:11 ` Joel Brobecker
2019-09-16 20:02 ` Joseph Myers
2019-09-17 11:13 ` Gerald Pfeifer
2019-09-17 12:55 ` Joel Brobecker
2019-09-17 15:56 ` Joseph Myers
2019-09-16 15:06 ` Joel Brobecker
2019-09-26 12:41 ` Joel Brobecker
2020-01-09 14:26 ` Joseph Myers
2020-01-09 22:07 ` Joseph Myers
2020-01-10 11:03 ` Jonathan Wakely
2020-01-10 13:06 ` Joseph Myers
2020-01-10 13:38 ` Jonathan Wakely
2020-01-10 15:53 ` Joseph Myers
2020-01-10 18:00 ` Joel Brobecker
2020-01-10 18:15 ` Joseph Myers
2020-01-10 18:22 ` Joel Brobecker
2020-01-10 18:24 ` Joseph Myers
2020-01-10 18:40 ` Joel Brobecker
2020-01-10 20:44 ` Joseph Myers
2020-01-13 20:47 ` Joseph Myers
2020-01-10 17:57 ` Joel Brobecker
2020-01-10 17:38 ` Joel Brobecker
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.21.1909151205100.19246@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jason@redhat.com \
--cc=maxim.kuvyrkov@linaro.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).