On 2005-05-12 13:44:55 -0700, Tim Hill wrote:
----8<----
> Why is this good? Because it eliminates drudge work for developers,
> because it frees the message log field for informal comments, and not
> quasi-data and because it encourages automation. At present, I have
> several processes I *cannot* automate easily in SVN because the "best
> practice" follows the familiar "search the log for the infomation, and
> type in the rev# into the -r switch" form. This is error-prone to automate.
>
> ok, you probably think I'm mad now :)
>
> --Tim
----8<----
Hear hear!
Personally I'm not *too* dissatisfied with the /tags solution for
labels, but I would love to be able to easily find the answer to
questions like "Show all log messages where rev property issue-number is
123", or "List all files in rev 27 where property svn:content-type is
txt/html". Of course, it would also be fairly easy to layer labels on
top of something like this with a "blessed" svn:label revprop or
somesuch.
Maybe something like:
svn log --revprop-search NAME VALUE PATH
and
svn ls --prop-search NAME VALUE PATH
I think the main thing holding this kind of functionality back is that
AFAIK, neither revision properties nor file properties are indexed, so
searching them would be very slow.
I'd be curious to hear from the developers if there is philosophical
opposition to implementing this kind of feature or if it's just that
no one has volunteered to do the work?
-Dominic
--
In the final reckoning there is only love, only that divinity. That we
are capable only of being what we are remains our unforgivable sin.
- application/pgp-signature attachment: stored
Received on Fri May 13 06:11:21 2005