Specialized feature request (custom revprop columns)

3 views
Skip to first unread message

Hans-Emil Skogh

unread,
Jul 2, 2009, 8:28:26 AM7/2/09
to d...@tortoisesvn.tigris.org
Hi all!
 
We have started to use revprops to track what revisions that have been subject to code review. While not optimal in every way, it's fairly simple and works well.
 
When starting to use revprops like this I realized that it would be very handy indeed if the log-dialog could be configured to show custom columns with revprops. For us it would be great to have a column showing the code review status of every revision directly in the log dialog.
 
I realize that this is a very specialized request, and I'm not even sure that it is feasible (do we have all revprops in the log cache?), but maybe it would be something that could be added to the issue tracker?
 
Hans-Emil

Stefan Küng

unread,
Jul 2, 2009, 2:12:09 PM7/2/09
to d...@tortoisesvn.tigris.org

Yes, the revprops are kept in the log cache. And here also lies the
problem with your approach:
If you use the revprops to set the code review state, then change that
reprop later to update the state, it wouldn't show up in the log dialog
because the original (first) state of your review is already in the cache.

Stefan

--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2367540

To unsubscribe from this discussion, e-mail: [dev-uns...@tortoisesvn.tigris.org].

signature.asc

Hans-Emil Skogh

unread,
Jul 3, 2009, 2:32:20 AM7/3/09
to d...@tortoisesvn.tigris.org
>> When starting to use revprops like this I realized that it would be very
>> handy indeed if the log-dialog could be configured to show custom
>> columns with revprops.
> If you use the revprops to set the code review state, then change that
> reprop later to update the state, it wouldn't show up in the log dialog
> because the original (first) state of your review is already in the cache.
Hmm... Of course, I see. That doesn't really seem to be a solvable problem within the current scope of the design. I guess the cache has (or could get) some function to update the revprops, but there isn't really any good way to know when to do such an update.
 
Or the refresh-button could be used to manually force an update of the revprops if custom revprop columns are shown, maybe that would be a usable if not ideal solution..? Or yet another button that is displayed when custom revprop columns are enabled? *sigh* Any other ideas out there?
 
Hans-Emil
Reply all
Reply to author
Forward
0 new messages