From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Jing Luo <jing@jing.rocks>, pve-devel@lists.proxmox.com
Subject: [pve-devel] applied: [PATCH proxmox-perl-rs] common: buildsys: Makefile: drop `--no-pre-clean`
Date: Mon, 11 Nov 2024 11:42:04 +0100 [thread overview]
Message-ID: <b153a4be-9107-4d30-b0ac-0765566b12e3@proxmox.com> (raw)
In-Reply-To: <20240927134831.2655916-2-jing@jing.rocks>
Am 27.09.24 um 15:45 schrieb Jing Luo:
> There is no difference in the source or binary packge running with or
> without `--no-pre-clean`. On the other hand, dpkg-buildpackge complains
> loudly when `--no-pre-clean` is specified, so let's remove it.
>
> Signed-off-by: Jing Luo <jing@jing.rocks>
> ---
> common/pkg/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
applied, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-11-11 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240927134831.2655916-1-jing@jing.rocks>
2024-09-27 13:45 ` [pve-devel] " Jing Luo via pve-devel
2024-11-11 10:41 ` [pve-devel] applied: [PATCH proxmox-perl-rs] common: d/control: change binary package architecture from `any` to `all` Thomas Lamprecht
[not found] ` <20240927134831.2655916-2-jing@jing.rocks>
2024-11-11 10:42 ` Thomas Lamprecht [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=b153a4be-9107-4d30-b0ac-0765566b12e3@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=jing@jing.rocks \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox