Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Sat, 8 Nov 2003 16:04:26 -0500
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: New tar available for testing (was Re: here is a patch for gnu tar incremental backup...)
Message-ID: <20031108210426.GA5429@redhat.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <7662849.1067255132356.JavaMail.cyyang@brunch.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7662849.1067255132356.JavaMail.cyyang@brunch.mit.edu>
User-Agent: Mutt/1.4.1i

On Mon, Oct 27, 2003 at 06:45:32AM -0500, George Carrette wrote:
>Here is a fix for gnu tar incremental backup feature
>for the most recent cygwin that uses a 64-bit value for 
>the type ion_t
>
>This was done against the sources in release/tar/tar-1.13.25-3-src.tar.bz2

Thanks for the patch but I don't think it is quite right and I don't think
it catches everything.

I'm uploading a new version of tar for testing now.  I'd appreciate feedback
(to the cygwin list) on whether it solves the reported problem.

cgf

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