On Tue, 14 Nov 2006, CVS list wrote:
Thanks Scott. It's good to get reassurance. Would you be willing to
share something of the changelog - not the content, but how it "works"
(or can anyone point me to a resource on changelog good practice).
Good changelogs are more synthetic than a bunch of commit messages, but it
helps to use the CVS changelog as a basis, and cvs2cl works well for me.
http://www.red-bean.com/cvs2cl/
For example, I use the following function in my scripts:
#############
cl_delta() {
# CAUTION: cvs rlog DEMANDS that there is NO space after -r
cvs rdiff -r $1 -r $2 $module \
| lsdiff \
| xargs cvs rlog -r$1::$2 \
| cvs2cl --rcs /cvsroot/$module --stdin --stdout \
--hide-filenames
if [ $verbose -gt 1 ]; then
cvs rdiff -r $1 -r $2 $module | diffstat
fi
}
#############
And use it to generate a log of commits between two tags on the same
branch:
$ cl_delta tag1 tag2
I don't know how meaningful it is for tags on different branches.
Cheers,
--
Jean-Marc Saffroy - [EMAIL PROTECTED]
_______________________________________________
info-cvs mailing list
info-cvs@nongnu.org
http://lists.nongnu.org/mailman/listinfo/info-cvs
