From: Danny S. <dan...@cl...> - 2006-01-11 23:31:54
|
----- Original Message ----- From: "Keith Marshall" Sent: Thursday, 12 January 2006 11:48 On Tuesday 10 January 2006 11:29 pm, Earnie Boyd wrote: [Re: MinGW CVS updates synchronised to Cygwin versioned releases] > > Just curious, but why is it done this way? Would it not make more sense > > for us MinGW developers to control our own release cycles, from our own > > CVS, and have the Cygwin folks synchronise their codebase to ours, when > > they are preparing their versioned releases? > > Historical reasons. The mingw-runtime and w32api started life in Cygwin. So, there is no technical reason then? For the w32api there is good tech reason to keep winsup as primary repository. Cygwin also depends on w32api and keeping in winsup means that changes are tested by cygwin developers very quickly. In past, they have caught quite a few bad commits by myself and other mingw developers. This timely feedback is valuable. To a lesser extent, mingw-runtime changes are also tested by cygwin developers through builds of mingw-dependent setup.exe Danny |