From: Lukas Wagner <l.wagner@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Christian Ebner <c.ebner@proxmox.com>
Subject: Re: [pbs-devel] [PATCH backup stable-2 1/3] pbs2to3: fix typo s/neighter/neither/
Date: Thu, 29 Jun 2023 08:59:43 +0200 [thread overview]
Message-ID: <1170115a-d36c-26b7-f4ea-864dcbea0caa@proxmox.com> (raw)
In-Reply-To: <20230628154054.1272-2-c.ebner@proxmox.com>
On 6/28/23 17:40, Christian Ebner wrote:
> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
> ---
> src/bin/pbs2to3.rs | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/bin/pbs2to3.rs b/src/bin/pbs2to3.rs
> index a3aa2816..168c9f00 100644
> --- a/src/bin/pbs2to3.rs
> +++ b/src/bin/pbs2to3.rs
> @@ -296,7 +296,7 @@ impl Checker {
> if suite != OLD_SUITE && suite != NEW_SUITE {
> let location = repo_file.path.clone().unwrap_or_default();
> self.output.log_notice(format!(
> - "found unusual suite '{suite}', neighter old '{OLD_SUITE}' nor new \
> + "found unusual suite '{suite}', neihter old '{OLD_SUITE}' nor new \
s/neihter/neither/ ? :D
> '{NEW_SUITE}'..\n Affected file {location}\n Please \
> assure this is shipping compatible packages for the upgrade!"
> ))?;
--
- Lukas
next prev parent reply other threads:[~2023-06-29 7:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 15:40 [pbs-devel] [PATCH backup stable-2 0/3] followup fixes for pbs2to3 Christian Ebner
2023-06-28 15:40 ` [pbs-devel] [PATCH backup stable-2 1/3] pbs2to3: fix typo s/neighter/neither/ Christian Ebner
2023-06-29 6:59 ` Lukas Wagner [this message]
2023-06-29 7:10 ` Christian Ebner
2023-06-28 15:40 ` [pbs-devel] [PATCH backup stable-2 2/3] pbs2to3: fix whitespaces Christian Ebner
2023-06-28 15:40 ` [pbs-devel] [PATCH backup stable-2 3/3] pbs2to3: set failure messages to bold Christian Ebner
2023-06-28 16:01 ` [pbs-devel] [PATCH backup stable-2 0/3] followup fixes for pbs2to3 Christian Ebner
2023-06-29 5:54 ` [pbs-devel] applied-series: " 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=1170115a-d36c-26b7-f4ea-864dcbea0caa@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=c.ebner@proxmox.com \
--cc=pbs-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