From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: [pve-devel] applied: [PATCH proxmox-backup-qemu] build: track symbols
Date: Fri, 12 Feb 2021 15:35:58 +0100 [thread overview]
Message-ID: <f8027191-fe9f-6d83-1bb8-fafec82668ce@proxmox.com> (raw)
In-Reply-To: <20210209112933.2654904-2-f.gruenbichler@proxmox.com>
On 09.02.21 12:29, Fabian Grünbichler wrote:
> for easier auto-generation of versioned deps. when adding new symbols,
> the build should display a warning + diff (in addition to our manual
> tracking of the generated header file). changes in symbol signatures or
> semantics are not caught automatically by the symbols file, but still
> require bumping the minimum library version for that symbol accordingly.
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
> this reflects the current state in master - the masterkey patch changes
> proxmox_backup_new to 1.0.3 or whatever the post-bump version is..
done
>
> debian/libproxmox-backup-qemu0.symbols | 34 ++++++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
> create mode 100644 debian/libproxmox-backup-qemu0.symbols
>
>
applied, thanks!
next prev parent reply other threads:[~2021-02-12 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 11:29 [pve-devel] [PATCH qemu] build: drop explicit libproxmox-backup-qemu0 dep Fabian Grünbichler
2021-02-09 11:29 ` [pve-devel] [PATCH proxmox-backup-qemu] build: track symbols Fabian Grünbichler
2021-02-12 14:35 ` Thomas Lamprecht [this message]
2021-02-12 14:36 ` [pve-devel] applied: [PATCH qemu] build: drop explicit libproxmox-backup-qemu0 dep Thomas Lamprecht
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=f8027191-fe9f-6d83-1bb8-fafec82668ce@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.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.