From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Prasad J Pandit <pjp@fedoraproject.org>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [Qemu-devel] [web PATCH 0/4] Add web section reporting information about CVEs in QEMU
Date: Fri, 19 Oct 2018 14:08:37 +0200 [thread overview]
Message-ID: <a7cec56c-5871-8a98-42f9-506f9b215569@redhat.com> (raw)
In-Reply-To: <20181019102528.GG13722@redhat.com>
On 19/10/2018 12:25, Daniel P. Berrangé wrote:
> I really don't want to use an application specific templating system.
> While we're using Jekyll for the website today, I don't think it is
> a good idea to assume that for the longer term.
>
> Even today I can't actually run the jekyll website on my laptop because
> the qemu-web content uses templating syntax from an older version of
> Jekyll that has been deleted in the current Jekyll versions. So I have
> to hack the code to remove pieces, in order to do testing.
Note that you can use
bundle install --path .gems
bundle exec jekyll serve
in order to use locally-downloaded gems.
That said, we should indeed update Jekyll to a more recent version.
Paolo
prev parent reply other threads:[~2018-10-19 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 14:51 [Qemu-devel] [web PATCH 0/4] Add web section reporting information about CVEs in QEMU Daniel P. Berrangé
2018-10-18 14:52 ` [Qemu-devel] [web PATCH 1/4] Underline the current page section Daniel P. Berrangé
2018-10-18 14:52 ` [Qemu-devel] [web PATCH 2/4] Introduce content and tools for managing security notices Daniel P. Berrangé
2018-10-18 14:52 ` [Qemu-devel] [web PATCH 3/4] Add vulnerability reports for 2018 Daniel P. Berrangé
2018-10-18 14:52 ` [Qemu-devel] [web PATCH 4/4] Update pre-rendered content Daniel P. Berrangé
2018-10-18 21:36 ` [Qemu-devel] [web PATCH 0/4] Add web section reporting information about CVEs in QEMU Paolo Bonzini
2018-10-19 10:25 ` Daniel P. Berrangé
2018-10-19 12:08 ` Paolo Bonzini [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=a7cec56c-5871-8a98-42f9-506f9b215569@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=pjp@fedoraproject.org \
--cc=qemu-devel@nongnu.org \
--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).