On Jun 9 15:43, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> >> I do not think I explained myself properly, sorry: Cygwin would
> >> previously read the
> >> obcaseinsensitve value under Windows 2000 to emulate the case
> >> insensitive behaviour of Windows XP and newer where obcaseinse
On Jun 5 18:28, Corinna Vinschen wrote:
> On Jun 6 01:02, Shaddy Baddah wrote:
> > On 2013-06-05 19:39+1000, Corinna Vinschen wrote:
> > >- Drop support for Windows 2000 and Windows XP pre-SP3.
> >
> > I find this change interesting. In no way am I complaining about this,
> > releases matching t
Greetings, Corinna Vinschen!
>> I do not think I explained myself properly, sorry: Cygwin would
>> previously read the
>> obcaseinsensitve value under Windows 2000 to emulate the case
>> insensitive behaviour of Windows XP and newer where obcaseinsensitive
>> was present in the registry.
>>
>> Th
On Jun 7 14:29, Nick Lowe wrote:
> I do not think I explained myself properly, sorry: Cygwin would
> previously read the
> obcaseinsensitve value under Windows 2000 to emulate the case
> insensitive behaviour of Windows XP and newer where obcaseinsensitive
> was present in the registry.
>
> The r
> Nick, was it you, who wrote this article?
> http://www.nicklowe.org/2012/02/understanding-case-sensitivity-in-windows-obcaseinsensitive-file_case_sensitive_search/
> Thanks for it, if so.
> But the more frustrating it makes your post, as article clearly states, that
I did, yes. I was trying to g
I do not think I explained myself properly, sorry: Cygwin would
previously read the
obcaseinsensitve value under Windows 2000 to emulate the case
insensitive behaviour of Windows XP and newer where obcaseinsensitive
was present in the registry.
The registry key does not represent the active state
Greetings, Nick Lowe!
> I notice you are still reading in obcaseinsensitive in cygcheck.cc but
> this value is no longer used in Cygwin as you have dropped Windows
> 2000 support.
> Would it make sense to change the code there to show the actual state
> of case sensitivity?
Nick, was it you, who
Hi Nick,
On Jun 7 12:00, Nick Lowe wrote:
> Hi Corinna,
>
> I notice you are still reading in obcaseinsensitive in cygcheck.cc but
> this value is no longer used in Cygwin as you have dropped Windows
> 2000 support.
>
> Would it make sense to change the code there to show the actual state
> of
Hi Corinna,
I notice you are still reading in obcaseinsensitive in cygcheck.cc but
this value is no longer used in Cygwin as you have dropped Windows
2000 support.
Would it make sense to change the code there to show the actual state
of case sensitivity?
Kind regards,
Nick
--
Problem reports:
On Jun 6 01:02, Shaddy Baddah wrote:
> Hi Corinna,
>
> On 2013-06-05 19:39+1000, Corinna Vinschen wrote:
> >I just released Cygwin 1.7.19.
> >
> >
> >What's new:
> >===
> >
> >- Drop support for Windows 2000 and Windows XP pre-SP3.
>
> I find this change interesting. In no way am I compl
Hi Corinna,
On 2013-06-05 19:39+1000, Corinna Vinschen wrote:
I just released Cygwin 1.7.19.
What's new:
===
- Drop support for Windows 2000 and Windows XP pre-SP3.
I find this change interesting. In no way am I complaining about this,
releases matching the above are well past end-o
Hi Cygwin friends and users,
I just released Cygwin 1.7.19.
What's new:
===
- Drop support for Windows 2000 and Windows XP pre-SP3.
- Add support for building a 64 bit version of Cygwin on x86_64 natively.
- Add support for creating native symlinks (CYGWIN=winsymlinks:native or
CYG
12 matches
Mail list logo
