From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: rsync 3.2.0
Date: Thu, 25 Jun 2020 17:56:21 +0200
Message-ID: <62eaae57-7008-a8f7-1419-a9cfef064b0c@ipfire.org>
In-Reply-To: <10D1F12A-DEEC-4C23-93FD-A33CF9A919D2@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6210509206081028601=="
List-Id: <development.lists.ipfire.org>

--===============6210509206081028601==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi,

On 25.06.2020 17:35, Michael Tremer wrote:

> ...
>> Please note:
>>
>> 'rsync 3.2.1' just came out. I'm testing - and working on 'zstd 1.4.5'
>> (weekend, I think).
>>
>> If you want, we could skip 3.2.0 =3D> no need to merge this patch.
>>
>> I could mark 3.2.0 as 'superseded' in patchwork and we'll go straight to
>> 3.2.1.
> Yes, absolutely do that. There is no point in merging 3.2.0 if 3.2.1 is alr=
eady under works.

Ok. Done.

Besides, I took a look. ;-)

Right now on my ToDo-list (compiling):

rsync 3.2.1 (Is it ok if I take over the build options of IPFire 3.0!?)

popt 1.18 (With 1.16, we're more than 9 years behind...)

And - "because it stood in my way":
ntp 4.2.8p15

And last but not least:
zstd 1.4.5

Best,
Matthias

--===============6210509206081028601==--