From: "Daniel P. Berrange" <berrange@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH qemu] git-submodule.sh: Do not try writing to source directory if not necessary
Date: Tue, 24 Oct 2017 17:27:52 +0100 [thread overview]
Message-ID: <20171024162752.GA21671@redhat.com> (raw)
In-Reply-To: <20171024085853.32615-1-aik@ozlabs.ru>
On Tue, Oct 24, 2017 at 07:58:53PM +1100, Alexey Kardashevskiy wrote:
> The new git-submodule.sh script writes .git-submodule-status to
> the source directory every time no matter what. This makes it conditional.
>
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> ---
>
> I compile out of tree on a remote guest system where I mount the
> source directory as "readonly" and build directory as "rw" and
> scripts/git-submodule.sh tries writing to the source directory even when
> I manually update modules on a host machine which is quite annoying.
>
> Is this something acceptable? Or I am missing something here?
How did you update the modules - did you manually run 'git submodule update...'
or did you use the git-submodule.sh script on your host machine ?
If you run git-submodule.sh on the host, then it should save the status
file, and then when you run make on the guest system, it should notice
that you're already updated and never even invoke 'git-submodule.sh update'
I'm not against your proposal below, but I'm curious why you're seeing
'git-submodule.sh update' being run by make in the first place.
>
> ---
> scripts/git-submodule.sh | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/git-submodule.sh b/scripts/git-submodule.sh
> index d8fbc7e47e..b642994a67 100755
> --- a/scripts/git-submodule.sh
> +++ b/scripts/git-submodule.sh
> @@ -33,6 +33,8 @@ status)
> ;;
> update)
> git submodule update --init $modules 1>/dev/null 2>&1
> - git submodule status $modules > "${substat}"
> + substat_tmp=$(mktemp)
> + git submodule status $modules > "$substat_tmp"
> + diff "${substat_tmp}" "${substat}" || mv "${substat_tmp}" "${substat}"
> ;;
> esac
> --
> 2.11.0
>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-10-24 16:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 8:58 [Qemu-devel] [RFC PATCH qemu] git-submodule.sh: Do not try writing to source directory if not necessary Alexey Kardashevskiy
2017-10-24 16:27 ` Daniel P. Berrange [this message]
2017-10-24 16:33 ` Peter Maydell
2017-10-25 1:24 ` Alexey Kardashevskiy
2017-10-25 1:45 ` Alexey Kardashevskiy
2017-10-25 6:57 ` Daniel P. Berrange
2017-10-25 8:10 ` Alexey Kardashevskiy
2017-10-25 21:11 ` Daniel P. Berrange
2017-10-26 0:54 ` Alexey Kardashevskiy
2017-10-26 7:02 ` Daniel P. Berrange
2017-10-26 7:45 ` Alexey Kardashevskiy
2017-10-26 8:18 ` Peter Maydell
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=20171024162752.GA21671@redhat.com \
--to=berrange@redhat.com \
--cc=aik@ozlabs.ru \
--cc=qemu-devel@nongnu.org \
/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).