public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	overseers@gcc.gnu.org
Subject: Re: GCC wwwdocs move to git done
Date: Wed, 09 Oct 2019 09:44:00 -0000	[thread overview]
Message-ID: <CAH6eHdQP=7V=BJSotNrbDweVVoLUc3yW87NWMrDfjxcF3J1hBg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1910090021470.32747@digraph.polyomino.org.uk>

On Wed, 9 Oct 2019 at 01:28, Joseph Myers wrote:
>
> I've done the move of GCC wwwdocs to git (using the previously posted and
> discussed scripts), including setting up the post-receive hook to do the
> same things previously covered by the old CVS hooks, and minimal updates
> to the web pages dealing with the CVS setup for wwwdocs.

Thanks, Joseph.

I just pushed a change and although it worked and appeared on
gcc.gnu.org, I got an error message during the push:

remote: hooks/post-receive: line 14: /www/gcc/updatelog: Permission denied
remote:   Updating /www/gcc/htdocs/gcc-10/changes.html

  parent reply	other threads:[~2019-10-09  9:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09  0:27 Joseph Myers
2019-10-09  1:04 ` Frank Ch. Eigler
2019-10-09 15:06   ` Joseph Myers
2019-10-09 16:28     ` David Malcolm
2019-10-09  8:01 ` Thomas Schwinge
2019-10-09  9:44 ` Jonathan Wakely [this message]
2019-10-09 12:25   ` Iain Sandoe
2019-10-09 13:38     ` Christopher Faylor
2019-10-09 13:40       ` Iain Sandoe
2019-10-09 13:41       ` Christopher Faylor
2019-10-09 13:43       ` David Malcolm
2019-10-09 12:29   ` Mark Wielaard
2019-10-20 16:40 ` Gerald Pfeifer
2019-10-24  9:32 ` Jose E. Marchesi
2019-11-06 14:03 ` Georg-Johann Lay
2019-11-06 14:05   ` Georg-Johann Lay

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='CAH6eHdQP=7V=BJSotNrbDweVVoLUc3yW87NWMrDfjxcF3J1hBg@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=overseers@gcc.gnu.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).