From: Bill Stewart <bstewart@iname.com>
To: cygwin@cygwin.com
Subject: Re: Which rsync version is current?
Date: Wed, 27 May 2020 13:34:04 -0600 [thread overview]
Message-ID: <CANV9t=T6aMKV1UWWKAyc7pYFwKnDGdZa2ibBTzDcLAjsBaZZdA@mail.gmail.com> (raw)
In-Reply-To: <384428076.20200527221608@yandex.ru>
On Wed, May 27, 2020 at 1:20 PM Andrey Repin wrote:
> > When I run rsync --version, I see this:
> >
> > rsync version 3.2.0dev protocol version 31
> >
> > However the Cygwin Setup program says that my rsync is current and is
> > listed as this version:
> >
> > 3.1.3+20200429+gitf7746d0-1
> >
> > rsync.samba.org says the current version is 3.1.3.
> >
> > So...what's actually the latest? What's the difference between these?
>
> Run `which rsync` to see which one is responding to you.
>
> 3.2-dev is likely a snapshot from ongoing development branch.
`which rsync` outputs
/usr/bin/rsync
as expected.
What I am saying is that the Setup program says the installed version
is 3.1.3+20200429+gitf7746d0-1.
For that installed version, `rsync --version` says the version is 3.2.0dev
Thus it seems that "3.1.3+20200429+gitf7746d0-1" is really identical
to "3.2.0dev".
Is this statement correct?
If this statement is indeed correct, I would say that this is
confusing (at the least) and that Setup or the rsync source code (or
both) should be updated to reflect the correct version number.
Bill
next prev parent reply other threads:[~2020-05-27 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 18:35 Bill Stewart
2020-05-27 19:16 ` Andrey Repin
2020-05-27 19:34 ` Bill Stewart [this message]
2020-05-27 20:19 ` Ken Brown
2020-05-27 21:02 ` Bill Stewart
2020-05-28 2:58 ` Marco Atzeri
2020-05-28 13:48 ` Bill Stewart
2020-05-27 19:27 ` Andrey Repin
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='CANV9t=T6aMKV1UWWKAyc7pYFwKnDGdZa2ibBTzDcLAjsBaZZdA@mail.gmail.com' \
--to=bstewart@iname.com \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).