qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Peter Maydell" <peter.maydell@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Cc: Miroslav Rezanina <mrezanin@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH] docs: Fix virtiofsd.1 location
Date: Wed, 12 Feb 2020 17:51:47 +0100	[thread overview]
Message-ID: <625cd959-6031-0a27-f25b-e2be6dc7ec3a@redhat.com> (raw)
In-Reply-To: <CAFEAcA_VsdWJELxDuMJW9iaRsB-At_Dyf3Z6paOHWEp+VEhSgw@mail.gmail.com>

On 2/12/20 5:02 PM, Peter Maydell wrote:
> On Wed, 12 Feb 2020 at 14:28, Daniel P. Berrangé <berrange@redhat.com> wrote:
>>
>> On Wed, Feb 12, 2020 at 02:18:19PM +0000, Peter Maydell wrote:
>>> On Wed, 12 Feb 2020 at 13:16, Miroslav Rezanina <mrezanin@redhat.com> wrote:
>>>>
>>>> Patch 6a7e2bbee5 docs: add virtiofsd(1) man page introduced new man
>>>> page virtiofsd.1. Unfortunately, wrong file location is used as
>>>> source for install command. This cause installation of docs fail.
>>>>
>>>> Fixing wrong location so installation is successful.
>>>>
>>>> Signed-off-by: Miroslav Rezanina <mrezanin@redhat.com>
>>>
>>> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
>>>
>>> I noticed this in review of v1 of the patch
>>> https://patchew.org/QEMU/20200127162514.56784-1-stefanha@redhat.com/
>>> but missed that it hadn't been fixed in v2/v3.
>>
>> How come the mistake didn't break any of our CI ?  Looks like it
>> should have failed due to non-existing source file

We stopped testing in-tree builds 2 months ago:

commit bc4486fb233573e77b6e9ad6d6379afb5e37ad8c
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Wed Dec 11 15:33:49 2019 +0100

     ci: build out-of-tree

     Most developers are using out-of-tree builds and it was discussed 
in the past
     to only allow those.  To prepare for the transition, use 
out-of-tree builds
     in all continuous integration jobs.

> 
> I imagine all our CI setups use separate-build-dir and don't
> test 'make install'. This only shows up if you do build-in-source-tree
> and then 'make install'. (In a separate-build-dir setup, the
> MANUAL_BUILDDIR is the same as the actual build dir,
> which is the same as make's current working directory, so
> forgetting it in the install rune doesn't matter. In a build from
> the source tree, Sphinx requires the output to be to a
> different directory than the source, so we have to create
> a subdirectory to be the MANUAL_BUILDDIR.)
> 
> thanks
> -- PMM
> 



  reply	other threads:[~2020-02-12 16:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1908428819.7192207.1581512184275.JavaMail.zimbra@redhat.com>
2020-02-12 13:16 ` [PATCH] docs: Fix virtiofsd.1 location Miroslav Rezanina
2020-02-12 14:18   ` Peter Maydell
2020-02-12 14:26     ` Dr. David Alan Gilbert
2020-02-12 14:28     ` Daniel P. Berrangé
2020-02-12 16:02       ` Peter Maydell
2020-02-12 16:51         ` Philippe Mathieu-Daudé [this message]
2020-02-12 17:51           ` Peter Maydell
2020-02-13 10:31             ` Paolo Bonzini

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=625cd959-6031-0a27-f25b-e2be6dc7ec3a@redhat.com \
    --to=philmd@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=mrezanin@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).