[reviving an old thread]
On 03/08/2016 05:52 PM, Eric Blake wrote:
> On 03/08/2016 08:43 AM, Douglas Coup wrote:
>> Hello Cygwin community.
>>
>> I'm observing some unusual behavior with tar v1.28, running as part of
>> 32-bit Cygwin on a Windows 10 machine.
>
> I noticed this in your cygcheck
> Could be an accidental regression in my cygwin-specific patches betweenthe
> two versions. But I don't normally use or test on text-mounts, so
> I'll need confirmation that you are indeed experiencing the problem only
>
For what it's worth, I recently had the similar issues with Cygwin tar
on t
Greetings, Douglas Coup!
>> On 03/08/2016 08:43 AM, Douglas Coup wrote:
>>> Hello Cygwin community.
>>>
>>> I'm observing some unusual behavior with tar v1.28, running as part of
>
>>> 32-bit Cygwin on a Windows 10 machine.
>
>
>> I noticed this in your cygcheck output: > cygdrive prefix /cygd
On 03/08/2016 08:43 AM, Douglas Coup wrote:
> Hello Cygwin community.
>
> I'm observing some unusual behavior with tar v1.28, running as part of
> 32-bit Cygwin on a Windows 10 machine.
I noticed this in your cygcheck output:
> cygdrive prefix /cygdrive system text,noacl,posix=0,auto
Why are
4 matches
Mail list logo
