Previously I had asked if there were any tools to automatically sync
two repositories. The idea was to work with developers that might be
only occasionally connected, but using a local (to them) repository
that occasionally synched to the main (remote) one.
The email I received generally indicated that this was not a realistic
or feasible idea, because of conflicts.
However, I was thinking today about synching individual modules.
Suppose that I had two different directories, and checked the project
out in them. One for each of the two CVSROOT's.
I make changes in the local CVSROOT directory, then into the local
repository. When I connect to the main, I copy the code over to the
other directory, and check into that.
But why the constant copy?
CVS stores all the information about where the repository is in CVS/.
Why not permit multiple repository directories, CVS/, CVS1/, CVS2/,
etc.
Consider the benefits:
1. Permits tracking local changes separately from global changes
Although my environment is for an 'occasionally connected' person,
others might want to use this in permanently connected areas. Consider
environments where you want to prevent excessive branching on the
tree, but still want "commit early, commit often". By giving each
developer their own commit tree, you can still keep the central store
fairly clean.
2. ???
In any event, how hard would it be to add a left side of "-r<n>" for
repository n (I don't think that option is take, I can't think of ever
using it)?
Michael
