From: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: thuth@redhat.com
Subject: Re: [PATCH v2] git-submodule.sh: allow running in validate mode without previous update
Date: Fri, 23 Jun 2023 13:39:46 +0200 [thread overview]
Message-ID: <e1603f7667334c649f7109eaebb759162bfb55dc.camel@linux.ibm.com> (raw)
In-Reply-To: <20230622095254.52398-1-pbonzini@redhat.com>
On Thu, 2023-06-22 at 11:52 +0200, Paolo Bonzini wrote:
> The call to git-submodule.sh done in configure may happen without a
> previous checkout of the roms/SLOF submodule, or even without a
> previous run of the script.
>
> So, handle creating a .git-submodule-status file even in validate
> mode. If git is absent, ensure that all passed directories exists
> (because you should be in a fresh untar and will not have stale
> arguments to git-submodule.sh) but do no other checks. If git
> is present, ensure that .git-submodule-status contains an entry
> for all submodules passed on the command line.
>
> With this change, "ignore" mode is not needed anymore.
>
> Reported-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
> Fixes: b11f9bd96f4 ("configure: move SLOF submodule handling to pc-bios/s390-ccw", 2023-06-06)
Reviewed-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
Tested-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> configure | 2 +-
> scripts/git-submodule.sh | 73 ++++++++++++++++++++++------------------
> 2 files changed, 42 insertions(+), 33 deletions(-)
[...]
> case "$command" in
> status|validate)
> - test -f "$substat" || validate_error "$command"
> - test -z "$maybe_modules" && exit 0
> for module in $modules; do
> - check_updated $module || validate_error "$command"
> + if is_git; then
> + check_updated $module || validate_error "$command"
> + elif ! (set xyz "$module"/* && test -e "$2"); then
You could also do set -- "$module"/* and use $1, not that it matters.
> + # The directory does not exist or it contains no files
> + echo "$0: sources not available for $module and $no_git_error"
> + validate_error "$command"
> + fi
> done
> - exit 0
> ;;
> +
> update)
> - test -e $substat || touch $substat
> - test -z "$maybe_modules" && exit 0
> + is_git || {
> + echo "$0: unexpectedly called with submodules but $no_git_error"
> + exit 1
> + }
>
> $GIT submodule update --init $modules 1>/dev/null
> test $? -ne 0 && update_error "failed to update modules"
prev parent reply other threads:[~2023-06-23 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 9:52 [PATCH v2] git-submodule.sh: allow running in validate mode without previous update Paolo Bonzini
2023-06-23 11:39 ` Nina Schoetterl-Glausch [this message]
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=e1603f7667334c649f7109eaebb759162bfb55dc.camel@linux.ibm.com \
--to=nsg@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).