qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [qemu-web PATCH] Add a blog post about FUSE block exports


From: Philippe Mathieu-Daudé
Subject: Re: [qemu-web PATCH] Add a blog post about FUSE block exports
Date: Thu, 19 Aug 2021 13:09:39 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0

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.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]