public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>,
	"Frank Ch. Eigler"	 <fche@elastic.org>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org, overseers@gcc.gnu.org
Subject: Re: GCC wwwdocs move to git done
Date: Wed, 09 Oct 2019 16:28:00 -0000	[thread overview]
Message-ID: <1570638534.5208.36.camel@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1910091505430.15557@digraph.polyomino.org.uk>

On Wed, 2019-10-09 at 15:06 +0000, Joseph Myers wrote:
> On Tue, 8 Oct 2019, Frank Ch. Eigler wrote:
> 
> > Hi -
> > 
> > Thanks - good job with moving this to git!

+1

> > > Note 1: someone with the right access needs to create the
> > > symlink 
> > > /sourceware/git/gcc-wwwdocs.git -> 
> > > /sourceware/projects/gcc-home/wwwdocs.git (and anything else
> > > needed for 
> > > anonymous git access to that repository).
> > 
> > Done.
> 
> Thanks!  I've now updated the instructions to use the shorter path to
> the 
> repository and restored the documentation of anonymous access.
> 
> diff --git a/htdocs/about.html b/htdocs/about.html
> index 30a5c943..019b6fbd 100644
> --- a/htdocs/about.html
> +++ b/htdocs/about.html
> @@ -54,10 +54,12 @@ a higher chance of being implemented soon. ;-
> )</p>
>  and SSH installed, you can check out the web pages as follows:</p>
>  
>  <ol>
> - <li><code>git clone git+ssh://<i>username</i>@gcc.gnu.org/sourcewar
> e/projects/gcc-home/wwwdocs.git</code>;
> + <li><code>git clone git+ssh://<i>username</i>@gcc.gnu.org/git/gcc-w
> wwdocs.git</code>;
>   where <i>username</i> is your user name at gcc.gnu.org</li>
>  </ol>
>  
> +<p>For anonymous access, use
> +<code>git://gcc.gnu.org/git/gcc-wwwdocs.git</code> instead.</p>
>  
>  <h3>Validating a change</h3>

Is there a web UI for viewing this new git repo?

I don't see it listed at:
  https://gcc.gnu.org/git/
(or would adding it there complicate the migration of the main repo?)

Thanks.

Dave

  reply	other threads:[~2019-10-09 16:28 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 [this message]
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

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=1570638534.5208.36.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=fche@elastic.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).