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

RE: Re: Adding an Inspection Id to each Log Message.

From: Reedick, Andrew <Andrew.Reedick_at_BellSouth.com>
Date: 2006-08-16 16:00:47 CEST

> -----Original Message-----
> From: Ryan Schmidt [mailto:subversion-2006c@ryandesign.com]
> 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.

Don't forget that it will be necessary to keep the two data sources in
sync. It is possible to change log messages after the commit, so you'll
need a post-revprop-change hook to update the database. Having two data
sources to keep in sync is the biggest drawback to using commit messages
to pass information to custom hooks or DBs.

Which is why I suggested this,
http://svn.haxx.se/users/archive-2006-08/0448.shtml, the ability to
parse out custom arguments on the command line (such as --bug_id or
--inspection_id) instead of relying on commit messages.


The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. 162

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 16 16:23:24 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.