qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: "Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	qemu-devel@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org,
	Greg Kurz <groug@kaod.org>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	stefanha@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [RFC] Move tools sources to the tools directory (was Re: [PATCH v2] MAINTAINERS: Fix the location of tools manuals)
Date: Thu, 4 Feb 2021 15:57:58 -0500	[thread overview]
Message-ID: <20baa37e-a6af-9732-b7fb-ad469f3907e0@redhat.com> (raw)
In-Reply-To: <0e0f9745-fe21-0bc6-2d02-431d67a6b57e@redhat.com>

On 2/4/21 9:22 AM, Wainer dos Santos Moschetta wrote:
> 
> On 2/4/21 10:59 AM, Philippe Mathieu-Daudé wrote:
>> On 2/4/21 2:54 PM, Wainer dos Santos Moschetta wrote:
>>> The qemu-img.rst, qemu-nbd.rst, virtfs-proxy-helper.rst, 
>>> qemu-trace-stap.rst,
>>> and virtiofsd.rst manuals were moved to docs/tools, so this update 
>>> MAINTAINERS
>>> accordingly.
>>>
>>> Fixes: a08b4a9fe6c ("docs: Move tools documentation to tools manual")
>>> Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
>>> ---
>>> v1: was "MAINTAINERS: Fix the location of virtiofsd.rst"
>>> v2: Fixed the location of all files [philmd]
>>>
>>>   MAINTAINERS | 10 +++++-----
>>>   1 file changed, 5 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 00626941f1..174425a941 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -1829,7 +1829,7 @@ S: Odd Fixes
>>>   F: hw/9pfs/
>>>   X: hw/9pfs/xen-9p*
>>>   F: fsdev/
>>> -F: docs/interop/virtfs-proxy-helper.rst
>>> +F: docs/tools/virtfs-proxy-helper.rst
>> Unrelated, but Paolo once said helpers are not tools.
> 
> Unrelated too, but allow me to ask:
> 
> Should we move the tools (qemu-img, qemu-io, qemu-nbd...etc) to the 
> tools directory (virtiofsd seems to feel alone there)?
> 

Only smiles and cheers from me. I recommend a README.rst that can go in 
the tools/ directory that explains the purpose of the directory and 
standards for inclusion, etc.

Very small blurbs explaining what, broadly, the tools are, could be nice 
for passers-by on gitlab while browsing the source structure.

This would allow us to codify much of what happened later in this thread 
(what goes here, why? do we support it? etc.)

--js



  parent reply	other threads:[~2021-02-04 20:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04 13:54 [PATCH v2] MAINTAINERS: Fix the location of tools manuals Wainer dos Santos Moschetta
2021-02-04 13:59 ` Philippe Mathieu-Daudé
2021-02-04 14:22   ` [RFC] Move tools sources to the tools directory (was Re: [PATCH v2] MAINTAINERS: Fix the location of tools manuals) Wainer dos Santos Moschetta
2021-02-04 14:31     ` Peter Maydell
2021-02-04 14:40       ` Kevin Wolf
2021-02-04 14:47         ` Daniel P. Berrangé
2021-02-04 14:50           ` Peter Maydell
2021-02-04 15:02             ` Paolo Bonzini
2021-02-04 15:06               ` Daniel P. Berrangé
2021-02-04 17:37                 ` Philippe Mathieu-Daudé
2021-02-04 17:39                   ` Paolo Bonzini
2021-02-04 15:04             ` Daniel P. Berrangé
2021-02-04 14:57           ` Kevin Wolf
2021-02-04 14:47         ` Peter Maydell
2021-02-04 14:40     ` Paolo Bonzini
2021-02-04 17:42       ` Philippe Mathieu-Daudé
2021-02-04 17:55         ` Paolo Bonzini
2021-02-04 18:24     ` Eric Blake
2021-02-04 20:57     ` John Snow [this message]
2021-03-09 17:41   ` [PATCH v2] MAINTAINERS: Fix the location of tools manuals Wainer dos Santos Moschetta
2021-03-09 19:48     ` Thomas Huth
2021-03-09 20:44       ` Laurent Vivier
2021-03-09 22:54       ` Greg Kurz

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=20baa37e-a6af-9732-b7fb-ad469f3907e0@redhat.com \
    --to=jsnow@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=groug@kaod.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=wainersm@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).