From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Hanna Reitz <hreitz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Thomas Huth <thuth@redhat.com>,
John Snow <jsnow@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [qemu-web PATCH] Add a blog post about FUSE block exports
Date: Thu, 19 Aug 2021 13:09:39 +0200 [thread overview]
Message-ID: <79bac137-bc68-2461-9ff2-84fe1659d19d@redhat.com> (raw)
In-Reply-To: <3d934aad-1676-19cf-ec8f-b3991efd6893@redhat.com>
On 8/19/21 1:00 PM, Hanna Reitz wrote:
> On 19.08.21 12:37, Philippe Mathieu-Daudé wrote:
>> On 8/19/21 12:25 PM, Hanna Reitz wrote:
>>> This post explains when FUSE block exports are useful, how they work,
>>> and that it is fun to export an image file on its own path so it looks
>>> like your image file (in whatever format it was) is a raw image now.
>>>
>>> Signed-off-by: Hanna Reitz <hreitz@redhat.com>
>>> ---
>>> You can also find this patch here:
>>> https://gitlab.com/hreitz/qemu-web fuse-blkexport-v1
>>>
>>> My first patch to qemu-web, so I hope I am not doing anything overly
>>> stupid here (adding SVGs with extremely long lines comes to mind)...
>> GitLab allows Mermaid and PlantUML diagrams in all tiers products:
>>
>> https://docs.gitlab.com/ee/user/markdown.html#diagrams-and-flowcharts
>> https://about.gitlab.com/handbook/markdown-guide/#diagrams
>>
>> I find the mermaid live editor easy to use:
>> https://mermaid-js.github.io/mermaid-live-editor/
>>
>> (I looked at that recently because I'd like the pages job to
>> generate QOM dependencies tree).
>
> Interesting, but it does seem limiting, so unless adding SVG graphs is
> unacceptable, I’d rather avoid it, to be honest...
Understandable ;) (I haven't said it is unacceptable).
However I expect long term text-based generated diagrams to be easier
to review. But I'm not sure, maybe the whole text is shuffled around
and this argument is pointless.
next prev parent reply other threads:[~2021-08-19 11:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 10:25 [qemu-web PATCH] Add a blog post about FUSE block exports Hanna Reitz
2021-08-19 10:37 ` Philippe Mathieu-Daudé
2021-08-19 11:00 ` Hanna Reitz
2021-08-19 11:09 ` Philippe Mathieu-Daudé [this message]
2021-08-19 11:17 ` Hanna Reitz
2021-08-19 16:23 ` Stefan Hajnoczi
2021-08-20 7:56 ` Hanna Reitz
2021-08-20 9:21 ` Daniel P. Berrangé
2021-08-20 14:27 ` Stefan Hajnoczi
2021-08-22 13:18 ` Thomas Huth
2021-08-23 8:30 ` Hanna Reitz
2021-08-23 8:49 ` Thomas Huth
2021-08-19 18:22 ` Klaus Kiwi
2021-08-20 9:03 ` Hanna Reitz
2021-08-20 21:24 ` Eric Blake
2021-08-23 8:23 ` Hanna Reitz
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=79bac137-bc68-2461-9ff2-84fe1659d19d@redhat.com \
--to=philmd@redhat.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@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).