|
From: Daniel J S. <dan...@ie...> - 2017-10-29 21:17:34
|
On 10/29/2017 03:34 PM, sfeam wrote: > On Sunday, 29 October 2017 14:01:15 Daniel J Sebald wrote: >> I've experimented with something called cvs2git, which I believe does a >> pretty good job of constructing branches and merges, but has some >> drawbacks. > > I think we are past the stage of looking for alternative conversion utilities. The point was something for comparison purposes and confirmation of the branch points for which cvs2git seems to match what I've been concluding, but others don't seem to trust. The reason for doing this is that we seem to be guessing at where things should go and how to devise shims to compensate. > Can't we just flatten everything prior to version 4.0 into a baseline > snapshot that is the root for everything subsequent to that? Spend time on that, or spend time to make that first dozen changesets in line with cvs2git. Whatever the case, we have to *start* from a point which is in agreement with the CVS repository so that the diffs going forward keep things in sync. > I really don't see why anyone will ever need to modify or branch from > anything prior to 4.0. The tarballs are good enough for historical > reference. I just don't see why anyone would care about the branch > structure of 3.4/3.5/3.7/3.8 now that it's 20 years done and over. I didn't suggest any effort to remove tags etc. Would have been fine with historical tags and whatever synthetic branches are added. What has mattered is recalling something from CVS and from the repository and have them match. Dan |