Paul Sander wrote: > You don't have to store the actual locations in the > repository. (Doing > so is pointless anyway given that mount points can appear and > disappear > non-deterministically.) Just store an identifier there, [etc]
Thank you for corroborating how difficult this would be to accomplish :-) To summarize: - you have to come up with a way of uniquely identifying each and every unique checkout. This includes scenarios such as: cvs co projname cd projname cvs edit filename cd .. rm -rf projname cvs co projname Two distinct checkouts, into the same location. - You have to manage these unique IDs, and maintain the correlation between the ID and the local directory - You have to come up with an administrative interface to manage manually removing edits to handle corner cases like the one above (or even the case above, without the second 'cvs co' command) I didn't say it couldn't be done, but I did hint that it would be a complicated job. To implement this feature would take a lot of thought and planning. A lot more than a simple patch to correct the "editors disappear on a checkout" bug that Darren fixed. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. ( http://www.leitch.com ) Columnist, C/C++ Users Journal ( http://www.cuj.com/experts ) _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
