[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Adding an Inspection Id to each Log Message.

From: Ryan Schmidt <subversion-2006c_at_ryandesign.com>
Date: 2006-08-16 01:38:21 CEST

On Aug 15, 2006, at 23:27, Royce Fessenden wrote:

> I would like to be able to add an Inspection Id to each log message
> so that we can track when and where the code was inspected. There
> would need to be a way to go back and enter the Id sometime after
> the initial commit. A way to list all code without an inspection
> Id is also needed.
> Is it possible to do what I want? If so, where can I find more
> information to get me started?

You can put anything you like into a log message. If you want to
require an inspection ID, write a pre-commit hook script that rejects
any commit whose message does not contain the inspection ID. On
error, print a message to the user advising them to include an
inspection ID.

If you want to be able to modify a revision's svn:log property (or
any other unversioned property) after the commit, you can install a
pre-revprop-change hook to allow this.

There is no way to search log messages, so there is no facility for
you to find code without an inspection ID. I suggest you set up a
separate (e.g. MySQL) database in which you have a record for each
revision. You can write a post-commit hook and a post-revprop-change
hook that write into this table whenever anybody includes an
inspection ID in their log message. From this you can determine which
revisions lack the property.

You could use the database to store more things as well. You could
put the entire log message into it, for example, so that you could
then use the database to perform searches on the log messages. You
could store other unversioned properties there as well.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 16 01:39:38 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.