From: Joseph Myers <joseph@codesourcery.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
Thomas Schwinge <thomas@codesourcery.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
Jason Merrill <jason@redhat.com>
Subject: Re: git conversion of GCC wwwdocs repository
Date: Wed, 25 Sep 2019 17:30:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1909251724450.21121@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20190925172215.GS9749@gate.crashing.org>
On Wed, 25 Sep 2019, Segher Boessenkool wrote:
> On Wed, Sep 25, 2019 at 04:49:58PM +0000, Joseph Myers wrote:
> > A version of the conversion using @gcc.gnu.org addresses is now available:
> >
> > git clone git+ssh://gcc.gnu.org/home/gccadmin/wwwdocs-test2.git
>
> This looks great, thanks!
>
> Can we test committing to this repo as well? Are hooks set up already?
The hooks aren't set up. Setting up the hooks will involve moving various
directories around in /www/gcc on sourceware to replace CVS checkouts with
symlinks into a git checkout, i.e. it's part of the actual move from CVS
to git, since the main thing the hooks do is run the preprocessor to
update the live website.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-09-25 17:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 2:30 Joseph Myers
2019-09-24 20:46 ` Joseph Myers
2019-09-24 22:09 ` Jonathan Wakely
2019-09-24 22:15 ` Joseph Myers
2019-09-24 22:31 ` Jonathan Wakely
2019-09-25 2:51 ` Jason Merrill
2019-09-25 10:08 ` Thomas Schwinge
2019-09-25 11:03 ` Jonathan Wakely
2019-09-25 16:50 ` Joseph Myers
2019-09-25 17:22 ` Segher Boessenkool
2019-09-25 17:30 ` Joseph Myers [this message]
2019-09-25 17:17 ` Segher Boessenkool
2019-10-20 19:17 ` Gerald Pfeifer
2019-10-20 21:14 ` Andreas Schwab
2019-09-30 19:56 ` Joseph Myers
2019-10-04 9:23 ` Thomas Schwinge
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.1909251724450.21121@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=jwakely.gcc@gmail.com \
--cc=segher@kernel.crashing.org \
--cc=thomas@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).