On 12/12/2008 10:48 AM, Eric Blake wrote:
According to Corinna Vinschen on 12/12/2008 7:58 AM:
I don't think it's the right way to special case this for Cygwin in
kpathsea. This isn't exactly a Cygwin issue. The right thing to do
would be to change the test in a generic fashion from
if (st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 12/12/2008 7:58 AM:
> I don't think it's the right way to special case this for Cygwin in
> kpathsea. This isn't exactly a Cygwin issue. The right thing to do
> would be to change the test in a generic fashion from
>
On Dec 12 09:44, Ken Brown wrote:
> On 12/12/2008 9:31 AM, Corinna Vinschen wrote:
>> On Dec 11 13:14, Ken Brown wrote:
>>>
>>> I think you forgot to mention the change to st_nlink [1], which will
>>> affect some applications. For example, the kpathsea search library for
>>> texlive needs to be
On 12/12/2008 9:31 AM, Corinna Vinschen wrote:
On Dec 11 13:14, Ken Brown wrote:
I think you forgot to mention the change to st_nlink [1], which will affect
some applications. For example, the kpathsea search library for texlive
needs to be patched to accommodate the change. (I've sent the
On Dec 11 13:14, Ken Brown wrote:
> On 12/10/2008 3:34 PM, Corinna Vinschen wrote:
>> At the end of this mail you will find a more or less complete list of
>> changes from 1.5.x to 1.7.x.
>
> I think you forgot to mention the change to st_nlink [1], which will affect
> some applications. For exam
On Thu, Dec 11, 2008 at 1:14 PM, Ken Brown wrote:
> One other thing I've noticed, which I think is unrelated, is that there is a
> glitch in directory listing in emacs under cygwin 1.7: If you try to list a
> directory with control-x d, very often the directory listing makes it look
> like the dir
On 12/10/2008 3:34 PM, Corinna Vinschen wrote:
At the end of this mail you will find a more or less complete list of
changes from 1.5.x to 1.7.x.
I think you forgot to mention the change to st_nlink [1], which will
affect some applications. For example, the kpathsea search library for
texliv
> From: Corinna Vinschen
[snip]
> > Do you have a sense for what would make the next major release
> > cygwin2.dll and not cygwin1.dll? Obviously an API or ABI breakage
> > would require a new DLL name, but do you have something on the wish
> > list that would require that, which was put off th
On Dec 10 21:10, Warren Young wrote:
> Christopher Faylor wrote:
>> On Wed, Dec 10, 2008 at 05:41:38PM -0700, Warren Young wrote:
>>> Is this going to change for the next major release? There's an awful lot
>>> to absorb in this one.
>> If you mean for 1.9.x then there is no way to predict that.
Matt Wozniski wrote:
to have a list of what we get for being able to drop this cursed loadstone.
^^^
I lol'ed at the reference
Glad someone got it. :)
Why don't you run
On Wed, Dec 10, 2008 at 7:41 PM, Warren Young wrote:
> Can you talk about the positive consequences? Obviously there's a lot of
> backwards compatibility stuff you can now ignore, and undoubtedly a lot of
> compatibility code that you were able to remove. I see some features in the
> following li
Christopher Faylor wrote:
On Wed, Dec 10, 2008 at 05:41:38PM -0700, Warren Young wrote:
Corinna Vinschen wrote:
after a rather long period of time of development,
Is this going to change for the next major release? There's an awful lot
to absorb in this one.
If you mean for 1.9.x then there
On Wed, Dec 10, 2008 at 05:41:38PM -0700, Warren Young wrote:
> Corinna Vinschen wrote:
>> after a rather long period of time of development,
>
> Is this going to change for the next major release? There's an awful lot
> to absorb in this one.
If you mean for 1.9.x then there is no way to predi
Corinna Vinschen wrote:
after a rather long period of time of development,
Is this going to change for the next major release? There's an awful
lot to absorb in this one.
- No more support for Windows 95/98/Me.
Awesome.
Can you talk about the positive consequences? Obviously there's
Corinna,
I just want to take second to thank you for all the work you've done on
Cygwin. Cygwin has kept me sane in Windows environments for ?? years
now, and I can only guess at the amount of time you've spent on it.
It's a great tool and I really appreciate it.
thanks,
Colin Ingarfield
Au
Hi all,
after a rather long period of time of development, we're proud to start
public testing of the upcoming new major release of Cygwin. The version
number is 1.7.0 for the current test release and will be 1.7.x with some
x yet to be chosen for the final release. As of today, the planning is
16 matches
Mail list logo
