From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Zhao Liu <zhao1.liu@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Manos Pitsidianakis <manos.pitsidianakis@linaro.org>,
qemu-devel@nongnu.org, qemu-rust@nongnu.org
Subject: Re: [PATCH] subprojects: Update .gitignore for syn
Date: Tue, 30 Sep 2025 10:22:46 +0100 [thread overview]
Message-ID: <aNuhZucYzGodd3J1@redhat.com> (raw)
In-Reply-To: <aNubKjqYulKoLJ6q@intel.com>
On Tue, Sep 30, 2025 at 04:56:10PM +0800, Zhao Liu wrote:
> > IMHO we should get rid of all the version numbers, and use wildcard
> > matches instead, to eliminate the bug scenario entirely, as people
> > will repeatedly forgot to change these versions.
>
> (Manos had the similar comment before.)
>
> My thought is that exact matching could help identify outdated
> subprojects, notifying developers to clean them up and free up a little
> local space?
If developers want to free up space, the submodules are the least
of the problem, but at the same time easily handled with git commands.
I'd much rather optimize for eliminating this "busy work" of changing
ignored version numbers on every update.
Also if you are switching back & forth between branches, it is likely
that there will be different versions present in the subprojects dir,
and it would be desirable for them all to be ignored by git.
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 :|
prev parent reply other threads:[~2025-09-30 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 7:53 [PATCH] subprojects: Update .gitignore for syn Zhao Liu
2025-09-30 7:50 ` Philippe Mathieu-Daudé
2025-09-30 8:18 ` Zhao Liu
2025-09-30 8:00 ` Philippe Mathieu-Daudé
2025-09-30 8:08 ` Daniel P. Berrangé
2025-09-30 8:56 ` Zhao Liu
2025-09-30 9:22 ` Daniel P. Berrangé [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=aNuhZucYzGodd3J1@redhat.com \
--to=berrange@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-rust@nongnu.org \
--cc=zhao1.liu@intel.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).