From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: rsync 3.2.2
Date: Sun, 05 Jul 2020 18:51:00 +0200 [thread overview]
Message-ID: <83e7f1ec-fb6a-a3ad-370a-e8a399652714@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
Hi,
now it happened - rsync 3.2.2 is out and running. Earlier then I expected...
Before I do this, I'd rather ask:
Shall I mark the existing patch for 'rsync 3.2.1' as "superseded" and
send a new patch or shall I just send an update for the existing 3.2.1
patch? I want to leave 'zstd 1.4.5' and 'popt 1.18' as they are.
Opinions?
Best,
Matthias
next reply other threads:[~2020-07-05 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 16:51 Matthias Fischer [this message]
2020-07-06 10:01 ` Michael Tremer
2020-07-06 16:40 ` Matthias Fischer
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=83e7f1ec-fb6a-a3ad-370a-e8a399652714@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