DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:reply-to:to:message-id
	:subject:mime-version:references:content-type
	:content-transfer-encoding; q=dns; s=default; b=yQrCE90pvoa38WD5
	m+DvO3rAYvPpWww9OvVBGCJEsUKvisqwH+s7Me0z24Xa8IfJmJik9otDJH4heNSZ
	HSc6ItqYeePFltkZurVOQjCN44v5rwtGuuRtQYvYRRvfkVG34h1D72byOI0lhVRS
	XAznnQMpsvxxtIcs5m0UFLhFlr0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 29 Mar 2019 16:24:11 +0000 (UTC)
From: "Gerard Pinzone via cygwin" <cygwin@cygwin.com>
Reply-To: Gerard Pinzone <gpinzone@yahoo.com>
Reply-To: Gerard Pinzone <gpinzone@yahoo.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Message-ID: <977898697.13294391.1553876651564@mail.yahoo.com>
Subject: tar 1.29 exclude bug
MIME-Version: 1.0
References: <977898697.13294391.1553876651564.ref@mail.yahoo.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

The latest version of tar in Cygwin is currently 1.29, which contains a bug in how it handles excludes. I was able to get around my particular problem by rolling back to 1.28. However, 1.29 is about three years old and there are much newer versions available. Does anyone have any idea when tar 1.32 will be implemented?

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