From: Thomas Schwinge <thomas@codesourcery.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: git conversion of GCC wwwdocs repository
Date: Fri, 04 Oct 2019 09:23:00 -0000 [thread overview]
Message-ID: <87lfu03lvj.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1909301954240.1462@digraph.polyomino.org.uk>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
Hi Joseph!
On 2019-09-30T19:56:39+0000, Joseph Myers <joseph@codesourcery.com> wrote:
> As far as I can tell from the discussion, people are happy with the
> version of the conversion using @gcc.gnu.org addresses. When shall we (do
> a final conversion if there are any commits postdating that one and)
> switch over to it as the live repository, set up hooks and update
> documentation of editing the website?
Given that nobody has raised any adverse opinions: can do that anytime
now?
Doing 'wwwdocs' before the sources repository conversion, we can use it
as a testbed for hooks setup: commit/push hook obviously, but also
Bugzilla integration, and fast-forward-only requirement for the 'master'
branch, etc.
Grüße
Thomas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]
prev parent reply other threads:[~2019-10-04 9:23 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
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 [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=87lfu03lvj.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@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).