From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] tar: Update to 1.30 (V2)
Date: Wed, 06 Jun 2018 21:55:12 +0200 [thread overview]
Message-ID: <1e3f277d-53bf-65f7-2e78-b38275e31d83@ipfire.org> (raw)
In-Reply-To: <fcf0b540-eb74-6dbb-28df-534e4423cf3b@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 306 bytes --]
On 06.06.2018 21:49, Matthias Fischer wrote:
> Hi,
>
>> did you test our backup and restore scripts as well? Are they affected by any of
>> these changes?
> Twice: Yes.
^^^
Sorry, I meant YES / NO!
I tested the backup and restore scripts: they ran without problems.
Best,
Matthias
next prev parent reply other threads:[~2018-06-06 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fb10fb9d-c59d-1e47-6287-bb4948c528e3@ipfire.org>
2018-06-06 12:32 ` Michael Tremer
2018-06-06 19:49 ` Matthias Fischer
2018-06-06 19:55 ` Matthias Fischer [this message]
2018-06-07 19:33 ` Michael Tremer
2018-05-29 18:42 Matthias Fischer
2018-05-29 19:36 ` Michael Tremer
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=1e3f277d-53bf-65f7-2e78-b38275e31d83@ipfire.org \
--to=matthias.fischer@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