> For those interested in problem-free fixing of bugs in last > final release, 2.0.x branch was created at the time of the release, > and such work shall be done there. Volunteers may start it right > away by merging '[TOMERGE 2.0]' marked patches from trunk to > 2.0.x branch. This will ensure that users won't have to wait > for next major release to get any bugs fixed, but they can get > it much more quickly with 2.0.1.
I wanted to start this process and since I'm a mercurial user I cloned the repository. I then started to examine the Changelog and it looks like that some commits have changes that must be ported and some that shouldn't.... I'm not a svn user... I will check the syntax.. .I imagine there is a svn diff (from revision) (to revision) and then import this patch into mercurial harbour 2.0 branch _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
