From: Keith M. <kei...@us...> - 2012-01-07 22:49:16
|
On 07/12/11 14:08, Keith Marshall wrote: > I am following up on the issues raised in: > https://sourceforge.net/tracker/?func=detail&atid=102435&aid=3063296&group_id=2435 > https://sourceforge.net/tracker/?func=detail&aid=3447137&group_id=2435&atid=302435 > https://sourceforge.net/tracker/?func=detail&atid=102435&aid=3441135&group_id=2435 > > Initially, considering w32api, ... Guys, I've made a start on this; you may have noticed a few innocuous changes already pushed to CVS, on the way toward addressing the first two of the above tickets. If any of you would like to review any of the next round of patches I propose to commit, I've staged a copy of my working mercurial sandbox at: http://hg.code.sf.net/u/keithmarshall/w32api/summary There are two branches: one called 'trunk', which reflects the current state of CVS. The second is called 'config-cleanup'; starting from the changeset designated be418470d7eb, with log message commencing 'Add PACKAGE_RELEASE ...', this tracks the further changes I would like to commit. Unless I see any objections within the next seven days, I will begin merging these across to 'trunk' and committing to CVS. BTW, you may note that I am NOT tracking the state of the generated configure script in this sandbox. This has been a persistent thorn in my side, and the more I have to deal with it, the more convinced I become that it doesn't belong in CVS either. I would like to remove it. Any objections? -- Regards, Keith. |