On Thu, 23 Jan 2020 at 12:54, Dr. David Alan Gilbert (git)
<[email protected]> wrote:
>
> From: "Dr. David Alan Gilbert" <[email protected]>
>
> The following changes since commit 3e08b2b9cb64bff2b73fa9128c0e49bfcde0dd40:
>
>   Merge remote-tracking branch 
> 'remotes/philmd-gitlab/tags/edk2-next-20200121' into staging (2020-01-21 
> 15:29:25 +0000)
>
> are available in the Git repository at:
>
>   [email protected]:dagrh/qemu.git tags/pull-virtiofs-20200123
>
> for you to fetch changes up to 87509325f70c78a28683f9460699915ea3300091:
>
>   virtiofsd: add some options to the help message (2020-01-23 10:54:49 +0000)
>
> ----------------------------------------------------------------
> virtiofsd first pull
>
> Import our virtiofsd.
> This pulls in the daemon to drive a file system connected to the
> existing qemu virtiofsd device.
> It's derived from upstream libfuse with lots of changes (and a lot
> trimmed out).
> The daemon lives in the newly created qemu/tools/virtiofsd
>
> Signed-off-by: Dr. David Alan Gilbert <[email protected]>


>  docs/tools/conf.py                        |   16 +
>  docs/tools/index.rst                      |   14 +
>  docs/tools/virtiofsd-security.rst         |  118 ++

Do we really want a new top-level manual? This isn't
in the plan: https://wiki.qemu.org/Features/Documentation

What defines what goes in docs/tools rather than
docs/interop (like qemu-nbd and qemu-img do) ?

thanks
-- PMM

Reply via email to