From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: v2 version of borgbackup fuse patch set to fix bug#12611
Date: Tue, 02 Aug 2022 11:34:01 +0200 [thread overview]
Message-ID: <4a5bf671-0516-3a2e-7de8-598aae7a9dff@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 287 bytes --]
Hi Peter,
The v2 version of the borgbackup fuse patch set to fix bug#12611 has been built and tested and worked as expected. Have marked the old version in patchwork as superseded.
This v2 patch set is good to be merged in once it has been reviewed.
Best regards,
Adolf
next reply other threads:[~2022-08-02 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 9:34 Adolf Belka [this message]
2022-08-06 14:43 ` Peter Müller
2022-08-06 15:54 ` Michael Tremer
2022-08-06 21:42 ` Adolf Belka
2022-08-07 9:36 ` Peter Müller
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=4a5bf671-0516-3a2e-7de8-598aae7a9dff@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/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