From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Cc: qemu-devel@nongnu.org, alex.bennee@linaro.org,
Richard Henderson <richard.henderson@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] scripts: remove erroneous file that breaks git clone on Windows
Date: Wed, 23 Oct 2024 09:10:23 +0100 [thread overview]
Message-ID: <ZxivYKsXEYJh6mR1@redhat.com> (raw)
In-Reply-To: <20241023073914.895438-1-pierrick.bouvier@linaro.org>
On Wed, Oct 23, 2024 at 12:39:14AM -0700, Pierrick Bouvier wrote:
> This file was created by mistake in recent ed7667188 (9p: remove
> 'proxy' filesystem backend driver).
>
> When cloning the repository using native git for windows, we see this:
> Error: error: invalid path 'scripts/meson-buildoptions.'
> Error: The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
> ---
> scripts/meson-buildoptions. | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> delete mode 100644 scripts/meson-buildoptions.
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
>
> diff --git a/scripts/meson-buildoptions. b/scripts/meson-buildoptions.
> deleted file mode 100644
> index e69de29bb2d..00000000000
> --
> 2.39.5
With 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:[~2024-10-23 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 7:39 [PATCH] scripts: remove erroneous file that breaks git clone on Windows Pierrick Bouvier
2024-10-23 8:10 ` Daniel P. Berrangé [this message]
2024-10-24 11:21 ` Paolo Bonzini
2024-10-29 18:09 ` Pierrick Bouvier
2024-10-31 11:01 ` Michael Tokarev
2024-10-31 18:05 ` Pierrick Bouvier
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=ZxivYKsXEYJh6mR1@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).