Quoting Julien Lecomte <julien@...>:
> On 04/03/2006 21:07, Chris Sutcliffe wrote:
>>> We can remove ``w32api'' and ``runtime'' from project CVS AFAIC. We
>>> used to allow updates to both and then a messy merge would take place.
>>> I stopped allowing updates to the project CVS for ``runtime'' and
>>> ``w32api'' because it was easier for me to stop those updates than it
>>> was to stop the updates to winsup/w32api and winsup/mingw. I would
>>> merge changes to ``runtime'' and ``w32api'' when a release was made.
>>> Chris continues to do that merge now, but we can stop that as well.
>> This may reduce the confusion, as the 'w32api' and 'runtime'
>> repositories in the MinGW project CVS are pretty much always out of
>> date (other than when there has just been a release). It has the
>> added benefit of making my life a little easier as well. :)
> What about keeping the w32api & runtime always in sync with the winsup one ?
> I don't know if this is possible, but using the sf shell to create a
> cron update job that daily downloads the winsup modules, and then
> updates the sf cvs.
Not worth the headache. SF may at some point cease execution of the
cron process. They have done that in the past.