On Sun, Oct 21, 2012 at 01:32:41PM -0500, Yaakov (Cygwin/X) wrote:
>On Sun, 2012-10-21 at 13:10 -0400, Christopher Faylor wrote:
>>That said, is it time to ask the mingw.org stuff to relocate their CVS
>>repo? I could tar up the affected CVS directories for them if so.
>
>What about some CVSROOT/m
On Fri, 2012-10-19 at 11:33 -0500, Yaakov (Cygwin/X) wrote:
> I'll include those changes and post a new patch then.
Revised patches for toplevel, winsup, winsup/cygwin, winsup/lsaauth, and
winsup/utils attached. Tested on Cygwin and F17 with mingw32-headers
from rawhide.
Yaakov
2012-10-21 Yaa
On Sun, 2012-10-21 at 13:10 -0400, Christopher Faylor wrote:
> That said, is it time to ask the mingw.org stuff to relocate their
> CVS repo? I could tar up the affected CVS directories for them if
> so.
What about some CVSROOT/modules magic to exclude winsup/mingw and
winsup/w32api from a Cygwin
On Sun, Oct 21, 2012 at 01:33:20PM +0200, Corinna Vinschen wrote:
>On Oct 19 20:46, Corinna Vinschen wrote:
>>On Oct 19 11:33, Yaakov (Cygwin/X) wrote:
>>>On Fri, 2012-10-19 at 11:21 +0200, Corinna Vinschen wrote:
Other than that, I think it's good to go in after the 1.7.17 release.
I'll tr
On Sun, 2012-10-21 at 13:33 +0200, Corinna Vinschen wrote:
> On second thought... considering that w32api is now Mingw64 based, and
> considering that building Cygwin with this Mingw64 built w32api works
> fine... what do you guys think about a "once and for all" approach? Is
> it really necessary
On Oct 19 20:46, Corinna Vinschen wrote:
> On Oct 19 11:33, Yaakov (Cygwin/X) wrote:
> > On Fri, 2012-10-19 at 11:21 +0200, Corinna Vinschen wrote:
> > > Other than that, I think it's good to go in after the 1.7.17 release.
> > > I'll try to do the release at some point between now and Monday.
> >
