From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PATCH] docs: move CODING_STYLE into the developer documentation
Date: Wed, 24 Feb 2021 15:33:41 +0000 [thread overview]
Message-ID: <YDZx1WEpMPGZB+b9@redhat.com> (raw)
In-Reply-To: <YDZv9ROdREeN5o5u@stefanha-x1.localdomain>
On Wed, Feb 24, 2021 at 03:25:41PM +0000, Stefan Hajnoczi wrote:
> On Wed, Feb 24, 2021 at 12:19:25PM +0000, Daniel P. Berrangé wrote:
> > On Wed, Feb 24, 2021 at 12:15:05PM +0000, Stefan Hajnoczi wrote:
> > > On Tue, Feb 23, 2021 at 01:37:45PM +0000, Alex Bennée wrote:
> > > >
> > > > Philippe Mathieu-Daudé <philmd@redhat.com> writes:
> > > > > Or even better since we have a job pushing to Gitlab pages
> > > > > accessible on https://qemu-project.gitlab.io/qemu/:
> > > > >
> > > > > https://qemu-project.gitlab.io/qemu/devel/style.html
> > > > >
> > > > > Maybe the https://www.qemu.org/docs/ redirect should
> > > > > go to gitlab page now?
> > > >
> > > > It could do either, I think the result is exactly the same.
> > >
> > > Standarizing project infrastructure on GitLab CI seems good to me. That
> > > way developers will be able to reuse their CI knowledge and won't have
> > > to learn other systems (like readthedocs).
> > >
> > > However, I don't see .gitlab-ci.yml directives that build the docs and
> > > publish a static page yet. Is anyone volunteering to do this? (It can be
> > > done as a separate step from this patch.)
> >
> > The very last job (called 'pages') in .gitlab-ci.yml does this.
>
> Awesome! I have updated the qemu.org HTTP redirect to GitLab:
>
> https://qemu.org/docs/master/
>
> If anyone wants to discuss RTD vs GitLab docs hosting more, please go
> ahead. We can change the redirect again in the future, if necessary.
The downside with using a HTTP redirect is that user's still see the
particular hosting choice. So they are liable to bookmark these
links which will break if we move again.
Paolo had proposed a patch to rsync the CI content directly onto
qemu.org:
https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg04629.html
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-02-24 15:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 9:59 [PATCH] docs: move CODING_STYLE into the developer documentation Alex Bennée
2021-02-23 11:05 ` Claudio Fontana
2021-02-24 11:01 ` Alex Bennée
2021-02-23 11:07 ` Peter Maydell
2021-02-23 11:29 ` Philippe Mathieu-Daudé
2021-02-23 11:33 ` Philippe Mathieu-Daudé
2021-02-23 13:37 ` Alex Bennée
2021-02-24 12:15 ` Stefan Hajnoczi
2021-02-24 12:19 ` Daniel P. Berrangé
2021-02-24 15:25 ` Stefan Hajnoczi
2021-02-24 15:33 ` Daniel P. Berrangé [this message]
2021-03-01 16:13 ` Stefan Hajnoczi
2021-02-23 12:03 ` Alex Bennée
2024-02-25 16:55 ` Files without license statement Stefan Weil via
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=YDZx1WEpMPGZB+b9@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.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 NNTP newsgroup(s).