Fwd: Revision Properties Question

---------- Forwarded message ----------
From: David Weintraub <qazwart@gmail.com>
Date: Jun 20, 2005 3:48 PM
Subject: Re: Revision Properties Question
To: Mark Phippard <MarkP@softlanding.com>

> David Weintraub <qazwart@gmail.com> wrote on 06/20/2005 12:04:29 PM:
>
> > We have a requirement that any change in Subversion should require a
> > revision property called "bugnum" that contains the bug number (or
> > numbers) of the bugs that were fixed with this revision.
> >
> > I would like to enforce this in a hook. Is there a way I can via the
> > pre-commit hook to see whether a revision property was actually set?

On 6/20/05, Mark Phippard <MarkP@softlanding.com> wrote:
> It isn't possible to set a custom revision property as part of a commit,
> so it definitely isn't possible to enforce it with a hook. Revision
> properties can only be set after the commit. That is why we chose to just
> use the log message in the issue tracking integration we designed for GUI
> clients, and is implemented by TortoiseSVN and Subclipse.
>
> http://svn.collab.net/repos/tortoisesvn/trunk/doc/issuetrackers.txt
>

I first found out that I had to upgrade to Subversion 1.2 to get the
svnlook propget command to look at revision properties (Subversion
1.1.3 didn't work).

Now, I can use svnlook to see if a revision property is actually set
on a commit transaction, but as you pointed out, there's no way to set
a revision property.

So, is this considered a bug? I hate the fact Subversion keeps
overloading the log with all sorts of information. I guess it doesn't
really matter anyway since there is no easy way to search a revision
property for a particular value.

--
David Weintraub
qazwart@gmail.com
-- 
--
David Weintraub
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org