public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: rsync 3.2.2
Date: Mon, 06 Jul 2020 11:01:48 +0100	[thread overview]
Message-ID: <01E50C03-FAD9-47DA-AE85-F4B7D4DD7175@ipfire.org> (raw)
In-Reply-To: <83e7f1ec-fb6a-a3ad-370a-e8a399652714@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]

Hi,

> On 5 Jul 2020, at 17:51, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi,
> 
> now it happened - rsync 3.2.2 is out and running. Earlier then I expected...

Well, this happens.

> 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.

However, I would not say that it makes sense to update to this release unless there are some critical fixes in it. If there are aesthetic or other minor fixes in this release, I am sure we can skip one so that we keep enough space in the updates for the bigger stuff (Python, perl, etc.).

I am very happy with your effort, but we basically make every third patch from you land in a release now. That sounds like a lot of work that can be invested into all the other packages that we have maybe?

-Michael

> 
> Opinions?
> 
> Best,
> Matthias


  reply	other threads:[~2020-07-06 10:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-05 16:51 Matthias Fischer
2020-07-06 10:01 ` Michael Tremer [this message]
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=01E50C03-FAD9-47DA-AE85-F4B7D4DD7175@ipfire.org \
    --to=michael.tremer@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