From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Liviu Ionescu <ilg@livius.net>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Markus Armbruster <armbru@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] Add --with-branding-prefix and QEMU_BRANDING_PREFIX
Date: Mon, 14 Feb 2022 12:28:48 +0000 [thread overview]
Message-ID: <YgpLAAztd6qNTwmm@redhat.com> (raw)
In-Reply-To: <08631A61-4E68-4A3A-99DC-56C3FDD5A780@livius.net>
On Mon, Feb 14, 2022 at 02:18:13PM +0200, Liviu Ionescu wrote:
>
>
> > On 14 Feb 2022, at 14:06, Peter Maydell <peter.maydell@linaro.org> wrote:
> >
> > ... but the "v6.2.0-1-xpack-arm" pkgversion suffix works for this
> > purpose too.
>
> Currently I do not use any --pkgversion in my builds, so I guess that
> this is automatically generated by the meson script, and reflects the
> name of a custom branch in my fork; if I switch to using the upstream
> repo, this will probably be replace by some tag or commit id, which
> identifies the exact version, isn't it?
In a .git checkout, pkgversion defaults to "git describe --match 'v*' --dirty"
See scripts/qemu-version.sh
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:[~2022-02-14 12:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 11:35 [PATCH] Add --with-branding-prefix and QEMU_BRANDING_PREFIX Liviu Ionescu
2022-01-20 12:05 ` Liviu Ionescu
2022-01-27 12:23 ` Liviu Ionescu
2022-02-08 19:34 ` Liviu Ionescu
2022-02-08 19:58 ` Peter Maydell
2022-02-08 20:39 ` Liviu Ionescu
2022-02-09 9:57 ` Stefan Hajnoczi
2022-02-09 10:13 ` Liviu Ionescu
2022-02-09 11:30 ` Peter Maydell
2022-02-09 12:09 ` Liviu Ionescu
2022-02-09 12:25 ` Daniel P. Berrangé
2022-02-14 11:54 ` Liviu Ionescu
2022-02-14 12:06 ` Peter Maydell
2022-02-14 12:18 ` Liviu Ionescu
2022-02-14 12:28 ` Daniel P. Berrangé [this message]
2022-02-14 13:05 ` Liviu Ionescu
2022-02-14 13:07 ` Daniel P. Berrangé
2022-02-14 13:08 ` 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=YgpLAAztd6qNTwmm@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=ilg@livius.net \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.