Koen wrote: > Now, I'd like to know if CVS can help me in verifying step 4, > by listing for > me all the changes to my codebase between TAG_MyApp_1.0 and > TAG_MyApp_1.1. > Any advice? The diff and log suggestions earlier in this thread should fit the bill perfectly.
> Ideally, I would only get the changes to the files that are > included somehow > in my application (and not changes to files in the codebase that have > nothing to do with my application), but I realize that CVS > has no knowledge > of that, so I guess I'll just need to sift through the listed > changes for > the whole code base and look for the ones for which I know > they are included > in my application. If they aren't in the application, why are they in the repository? Reorganize your repository. Move any files not related to the application into different sections of the repository. Otherwise, you'll never have a clear idea of what makes up the application and what's irrelevant. -- 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 Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs