This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Re: upload: tar-1.15.1-2
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: The Cygwin-Talk Malingering List <cygwin-talk at cygwin dot com>
- Date: Fri, 19 Aug 2005 09:56:11 -0400
- Subject: Re: upload: tar-1.15.1-2
- References: <081720051820.16511.43037FFA000EC6140000407F22007348300A050E040D0C079D0A@comcast.net> <43048BF6.2050308@byu.net> <20050819075108.GA1216@efn.org>
- Reply-to: The Cygwin-Talk Malingering List <cygwin-talk at cygwin dot com>
- Reply-to: cygwin-talk at cygwin dot com
On Fri, Aug 19, 2005 at 12:51:08AM -0700, Yitzchak Scott-Thoennes wrote:
>On Thu, Aug 18, 2005 at 07:24:06AM -0600, Eric Blake wrote:
>> Meanwhile, I've noticed a problem with forcing text reads. Managed mounts
>> did not exist when 1.13.25-7 was released, so \r was never a valid
>> character in a filename, so forcing text mode on the -T file was not a
>> problem. But now that managed mounts exist, forcing text mode on a file
>> listing of a managed mount directory, when the file listing was prepared
>> in binary mode, will strip a trailing \r from the filename and do the
>> wrong thing. I went ahead and built 1.15.1-2 so that without --null,
>> there is no behavior changes from 1.13.25-7 (ie. still force text mode on
>> the -T file) as you have requested, but so you can now use --null -T to
>> specify files with trailing \r in a managed mount.
>
>Whew. Everybody collectively sighing in relief? Our trailing-\r
>named files are safe!
>
>(Just kidding; thanks for all the hard work, Eric.)
Double ditto.
cgf