DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:reply-to; q=
	dns; s=default; b=UuSYInZIXbfPnp8hbeB626JHenEhiATSzOX4G+LThmXTRb
	byll9MPSvXaJEZXqUJLxq+hHz5XsTWcnsuwc7agSm1nNTwlyB0OkNPFvv8xyPCH0
	zpTs7a0Kg3kDAn3Ju1dNJ51uHmzngbige8YVB/P3ioImx6shvKv6WTBxp/V6I=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: Will Parsons <wbp@nodomain.invalid>
Subject: Problem with Fossil version
Date: Thu, 19 Oct 2017 19:49:08 +0000 (UTC)
Lines: 12
Message-ID: <osavjk$d5a$1@blaine.gmane.org>
Reply-To: wbparsons@cshore.com
User-Agent: slrn/1.0.3 (CYGWIN_NT-6.1)

I've been using fossil as my SCM system of choice for some years now, and
have been in the habit of synching my repositories under Cygwin with those on
a remote Unix (FreeBSD) system.  Recently, though, I created a new repository
under FreeBSD and found I cannot clone it to Cygwin.

Apparently, this is due to an upgrade to fossil on the FreeBSD side, which is
now at version 2.2 while the Cygwin version is still 1.34, which seems to
date back to 2015.  Is there a specific reason the Cygwin fossil hasn't been
upgraded to a 2.x version?

-- 
Will


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple