From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Christoph Heiss <c.heiss@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH v2 container 1/4] lxc: Fix some trailing whitespace
Date: Fri, 17 Feb 2023 15:22:39 +0100 [thread overview]
Message-ID: <20230217142239.p5mptzcibs3pv5te@fwblub> (raw)
In-Reply-To: <20230215140245.496507-2-c.heiss@proxmox.com>
Does not apply, somewhere along the line you're stripping the trailing
newlines of these patches, how did you generate them?
On Wed, Feb 15, 2023 at 03:02:42PM +0100, Christoph Heiss wrote:
> No functional changes.
>
> Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
> ---
> Changes v1 -> v2:
> * New patch, split out from patch 2
>
> src/PVE/LXC.pm | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
> index ce6d5a5..345e343 100644
> --- a/src/PVE/LXC.pm
> +++ b/src/PVE/LXC.pm
> @@ -668,7 +668,7 @@ sub update_lxc_config {
>
> # some init scripts expect a linux terminal (turnkey).
> $raw .= "lxc.environment = TERM=linux\n";
> -
> +
> my $utsname = $conf->{hostname} || "CT$vmid";
> $raw .= "lxc.uts.name = $utsname\n";
>
> @@ -1703,14 +1703,14 @@ sub __mountpoint_mount {
> my $type = $mountpoint->{type};
> my $quota = !$snapname && !$mountpoint->{ro} && $mountpoint->{quota};
> my $mounted_dev;
> -
> +
> return if !$volid || !$mount;
>
> $mount =~ s!/+!/!g;
>
> my $mount_path;
> my ($mpfd, $parentfd, $last_dir);
> -
> +
> if (defined($rootdir)) {
> ($rootdir, $mount_path, $mpfd, $parentfd, $last_dir) =
> __mount_prepare_rootdir($rootdir, $mount, $rootuid, $rootgid);
> @@ -1719,7 +1719,7 @@ sub __mountpoint_mount {
> if (defined($stage_mount)) {
> $mount_path = $rootdir;
> }
> -
> +
> my ($storage, $volname) = PVE::Storage::parse_volume_id($volid, 1);
>
> die "unknown snapshot path for '$volid'" if !$storage && defined($snapname);
> @@ -1828,7 +1828,7 @@ sub __mountpoint_mount {
> warn "cannot enable quota control for bind mounts\n" if $quota;
> return wantarray ? ($volid, 0, undef) : $volid;
> }
> -
> +
> die "unsupported storage";
> }
>
> --
> 2.39.1
next prev parent reply other threads:[~2023-02-17 14:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 14:02 [pve-devel] [PATCH v2 container/manager 0/4] fix #3413: Add `Disconnect` option for LXC networks Christoph Heiss
2023-02-15 14:02 ` [pve-devel] [PATCH v2 container 1/4] lxc: Fix some trailing whitespace Christoph Heiss
2023-02-17 14:22 ` Wolfgang Bumiller [this message]
2023-02-20 11:13 ` Christoph Heiss
2023-02-15 14:02 ` [pve-devel] [PATCH v2 container 2/4] lxc: Avoid open-coding normal vs SDN-specific tap_plug() Christoph Heiss
2023-02-17 14:34 ` Wolfgang Bumiller
2023-02-20 11:17 ` Christoph Heiss
2023-02-15 14:02 ` [pve-devel] [PATCH v2 container 3/4] lxc: Add `link-down` config to allow setting interfaces as disconnected Christoph Heiss
2023-02-17 14:51 ` Wolfgang Bumiller
2023-02-17 16:38 ` Thomas Lamprecht
2023-02-20 11:51 ` Christoph Heiss
2023-02-20 12:33 ` Wolfgang Bumiller
2023-02-20 12:37 ` Thomas Lamprecht
2023-02-15 14:02 ` [pve-devel] [PATCH v2 manager 4/4] lxc: Add `Disconnect` option for network interfaces Christoph Heiss
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=20230217142239.p5mptzcibs3pv5te@fwblub \
--to=w.bumiller@proxmox.com \
--cc=c.heiss@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox