From: Ethan M. <merritt@u.washington.edu> - 2004-06-21 21:58:34
|
On Monday 21 June 2004 07:07 am, Hans-Bernhard Broeker wrote: > > *) If we move towards ANSI-C function definitions, I think that should > > be done *before* we split off a 4.0 branch, to reduce "patch distance" > > between the two branches. I'm in favour of doing that, with a tag > > 4.0.1 before we start it, and another tag (4.0.2) right afterwards. > > 4.0.2 would become the branch-off point for the 4.0-release branch. > > I've pretty much completed this monstrous editing job over the weekend. > Nothing in CVS yet, but it can now be pulled off at a moment's notice. Did you do this manually, or were you able to automate the procedure somehow? I ask with some trepidation since it seems likely that applying this to the cvs tree will break every patchset on SourceForge including a couple of large ones that I have been maintaining. That's not an argument against doing it, but I wonder if there is a way to apply your ANSIfication to both a patched and unpatched CVS tree in parallel so that I can regenerate the patchset to apply against the ANSIfied version. -- Ethan A Merritt merritt@u.washington.edu Biomolecular Structure Center Mailstop 357742 University of Washington, Seattle, WA 98195 |