public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Iain Sandoe <idsandoe@googlemail.com>
To: Christopher Faylor <cgf-use-the-mailinglist-please@gnu.org>
Cc: Joseph Myers <joseph@codesourcery.com>,
	"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 13:40:00 -0000	[thread overview]
Message-ID: <023B080D-3620-4865-89EC-CF72D435C573@googlemail.com> (raw)
In-Reply-To: <20191009133754.GA3268@cgf.cx>

Christopher Faylor <cgf-use-the-mailinglist-please@gnu.org> wrote:

> On Wed, Oct 09, 2019 at 01:25:30PM +0100, Iain Sandoe wrote:
>> Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>>
>>> 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.
>>
>> +1
>>
>> I would like to be able to preview changes to the website by using it
>> from a local
>> webserver.  I realise that individual pages can be viewed in a
>> browser / validated
>> by uploading - but it would be nice to check connectivity etc.
>>
>> At the moment, I can’t identify the “mhc” program that is used in
>> preparing the text
>> (and too many unrelated hits from searches).
>
> I think it's the "metahtml" processor:
>
> https://ftp.gnu.org/gnu/metahtml/
>
> The binary is 20 years old and, somehow, the source code used to build
> it seems to have disappeared.

Yeah - https://www.gnu.org/software/metahtml/

but the cvs co seems to hang on a lock :(

something to investigate later...
Iain

  reply	other threads:[~2019-10-09 13:40 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 [this message]
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=023B080D-3620-4865-89EC-CF72D435C573@googlemail.com \
    --to=idsandoe@googlemail.com \
    --cc=cgf-use-the-mailinglist-please@gnu.org \
    --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).