Cool, it's a very interesting tools. I definitely will try it out. However, I still want to find it out how should work with cvs first. Thanks very much, it is a very good suggestion.
On Mar 29, 2:25 am, [EMAIL PROTECTED] (Pierre Asselin) wrote: > jian <[EMAIL PROTECTED]> wrote: > You should investigate cvs2cl,http://www.red-bean.com/cvs2cl/. > It runs "cvs log" and collates the output in reverse chronological > order across all files. > > Yes ! Do exactly that. Commit all the changes related to bug 1234, > all at once. When you later run cvs2cl, the resulting ChangeLog > file show you all the files affected by that commit. > > The other thing you can do is tag milestones, even if only for > documentation purposes. Run "cvs2cl -t" put the tags in the > ChangeLog. > > -- > pa at panix dot com _______________________________________________ info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
