jpierre writes: > > Content-Type: text/html; charset=ISO-8859-1 > content-transfer-encoding: -SUGGEST
Please do not send MIME and/or HTML encrypted messages to the list. Plain text only, PLEASE! > cvs remove "works" in the sense that yes, the file gets removed from > the branch, when updating or checking out the branch. But on the > server, the file is still there, and tools that look on the server > (viewCVS, for example), still show the file. This means that all > scripts looking at the content on the repository will think that the > file is still in the branch. Of course the file is still on the server -- the whole point of a versioning system is to let you retreive old versions of a file, even one that has been deleted. The repository directory structure represents the contents of the trunk, not any other branch, and that's just an optimization that really shouldn't be depended on. Any script that thinks it can intuit the contents of a branch from the repository directory structure without examining the contents of the individual files is seriously broken. And it's a bad idea in general -- the repository should only be accessed with CVS commands, it should not be accessed directly. -Larry Jones Well, it's all a question of perspective. -- Calvin _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
