I have thought of that solution. The problem is, of all log messages in all files of the project, how do I find the log message that the user just wrote? Note that the commit could be made to a branch or to the trunk. I can easily find out what the branch is, but the log message only appears in those files that have actually been committed. I can, of course, check which files are to be committed, just before the "committed" - but I prefer to use a simpler method to achieve what I wanted, if possible.
Shlomo -----Original Message----- From: Jouni Heikniemi [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 17, 2002 11:47 AM To: Reinstein, Shlomo Cc: '[EMAIL PROTECTED]' Subject: Re: Automatically tagging the repository after (almost) every commit On Wed, 17 Jul 2002, Reinstein, Shlomo wrote: > Can I achieve the same if the repository sits in a CVS server? If so, how? > I realize that I can use "rtag" in the loginfo script to tag the repository, > knowing the 1st line of the commit message. But I don't know whether or not > I should tag the repository - this information is only in the first Perl > script. First, I'd question the need for that kind of tagging, but I hope you really know it's the best way to achieve whatever you're doing :-) I think you don't want to imagine (much less implement) the solution that it would take to get all those params etcetera to the loginfo script, so I suggest you start implementing all the tagging logic into the perl wrapper your users are running. Try doing a `cvs log` after the commit has finished, pick up the proper log message and then compose a tag. That way you wouldn't have to hook the loginfo for this purpose at all. Jouni _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
