Tate Austin writes:
>
> This is a multi-part message in MIME format.
Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!
> Hey, I have a CVS server we are trying to do is to specialize a release
> a bit, have the repository find the difference between what is currently
> on it and what the last version tag was. Then generate a patch based on
> that? So the idea being that every time we perform a release, it marks
> that release in CVS and so the next release it finds the difference
> between the current files and the state the files were in at the last
> tag in the cvs repository? Is this something cvs is capable of doing by
> default? (i'm new to using it beyond a distant file repository purpose)
It won't do it by itself, but it's quite easy to do:
cvs rtag V1 mystuff
(work on stuff for next release)
cvs rtag V2 mystuff
cvs patch -rV1 -rV2 mystuff >mystuff_V2.patch
(work on stuff for next release)
cvs rtag V3 mystuff
cvs patch -rV2 -rV3 mystuff >mystuff_V3.patch
(etc.)
-Larry Jones
They can make me do it, but they can't make me do it with dignity. -- Calvin
_______________________________________________
Info-cvs mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/info-cvs
