On Sat, Jan 06, 2007 at 07:36:29PM -0600, Carlo Marcelo Arenas Belon wrote: > wasn't really sure either about the accuracy of the 2.5.x tags, as I'd been so > far unsuccessful trying to match the 2.5.7 tag with the corresponding update > version in trunk
after going up and down in the versions for the tree, finally got the following references : trunk revision 242 = tag monitor-core-2.5.6 branch Version_2-5-7 revision 377 = tag monitor-core-2.5.7 sadly, the missing files seem to be gone from all the revisions I'd look for and I presume they were probably lost with the CVS to SVN migration. the problem being of course, that a gmond without "machines" (all the per platform metrics in the 2.x times) is pretty useless as it won't even configure, and with all the missing supporting files won't be able to compile. so we should probably drop those tags as they are of no use as is, with the old tar.gz being the only reliable source we got from the code. now for the maintenance branch for 2.5.x, since there is no way to start from the current code tree, anyone has any objections if I just commit the last tar.gz from version 2.5.7 and start a new history from that? or should we try to recover the old history and stabilize the tree even if that means affecting most likely the current development in HEAD?. Carlo
