[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#22845: FYI: release soon
From: |
Jim Meyering |
Subject: |
bug#22845: FYI: release soon |
Date: |
Mon, 29 Feb 2016 08:45:46 -0800 |
On Sun, Feb 28, 2016 at 10:54 PM, Paul Eggert <address@hidden> wrote:
> Jim Meyering wrote:
>>
>> I'll push this in the next day or so, so any improvements people
>> can suggest in the mean time would be most welcome.
>
>
> Thanks for doing all that.
>
> In NEWS, there should be one "New features" section, not two.
Good catch.
> I had difficulty following the new documentation. Perhaps it's because of
> the word "synchronize" and the recently-added --synchronous option. Also,
> the phrase "cannot tell the difference" is confusing -- it's trying to talk
> about the output of gunzip, not about gunzip itself. And "reduces
> compression" is ambiguous, since compression already reduces. How about
> something like the following instead?
>
> @item --rsyncable
> Cater better to the @command{rsync} program. Although does not compress
> quite as well, it lets the @code{rsync} program take advantage of
> similarities in the uncompressed input when synchronizing two files
> compressed with this flag.
Thank you. I prefer that, too. Tweaked slightly:
@item --rsyncable
Cater better to the @command{rsync} program by periodically resetting
the internal structure of the compressed data stream. This lets the
@code{rsync} program take advantage of similarities in the uncompressed
input when synchronizing two files compressed with this flag. The cost:
the compressed output is slightly larger.
Will post a revised patch to the proper list.