From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: rsync 3.2.3 + zstd 1.4.5 + ???
Date: Mon, 17 Aug 2020 18:55:00 +0200 [thread overview]
Message-ID: <bb5d927a-f779-6b85-2c48-a44d55e89033@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
Hi,
I don't want to make too much noise, so:
Although there hasn't been much time lately and the temperatures
contributed to it, I still have the following updates in the queue:
rsync 3.2.3 => Update to 3.2.3
zstd => 1.4.5 (new package, required for rsync)
Having in mind - could be ready perhaps on weekend:
libidn => Update to 1.36
libgcrypt => Update to 1.8.6
Is there any "room" for these updates or shall I wait? ;-)
Best,
Matthias
next reply other threads:[~2020-08-17 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 16:55 Matthias Fischer [this message]
2020-08-17 17:46 ` 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=bb5d927a-f779-6b85-2c48-a44d55e89033@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