public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Georg-Johann Lay <avr@gjlay.de>
To: Joseph Myers <joseph@codesourcery.com>,
	gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Cc: overseers@gcc.gnu.org
Subject: Re: GCC wwwdocs move to git done
Date: Wed, 06 Nov 2019 14:05:00 -0000	[thread overview]
Message-ID: <f4db0f40-fecb-a57f-4695-0be9401ac773@gjlay.de> (raw)
In-Reply-To: <a543092b-6976-0e49-ba87-1918ba79e5f9@gjlay.de>

Am 06.11.19 um 15:03 schrieb Georg-Johann Lay:
> Am 09.10.19 um 02:27 schrieb Joseph Myers:
>> 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.
> 
> Hi,
> 
> May it be the case that some parts are missing?  In particular, I cannot
> find the source of
> 
> https://gcc.gnu.org/install/configure.html
> 
> Johann
> 

Ok, found it in install/README. knew it had something special about it...

Johann




      reply	other threads:[~2019-11-06 14:05 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
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 [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=f4db0f40-fecb-a57f-4695-0be9401ac773@gjlay.de \
    --to=avr@gjlay.de \
    --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).