SteveKing <steveking@gmx.ch> writes:
> I'm not sure why you think this would be a *huge* complexity
> burden. TSVN already has locally stored log message templates
> implemented:
> tsvn:logtemplate
> http://tortoisesvn.tigris.org/docs/TortoiseSVN_en/ch04s09.html
How does TSVN handle it when it finds multiple such properties as it
crawls upwards, and they have different values?
How does TSVN handle it if the crawl to find a tsvn:logtemplate
property takes a long time? Does it just wait that long to show the
user a log message edit box, or does it show the box immediately and
then take further action later if it finds a template(s) during the
crawl?
Another way to ask that might be: What does TSVN do between the time
the user starts the commit and the time the user checkboxes the first
file or directory to be included in the commit?
As the user checks/unchecks different files and directories (perhaps
the user is indecisive and keeps changing his mind about what will be
in the commit), does TSVN re-crawl to discover whether the log message
template needs to change based on the new target paths? If it does,
how does the interface handle the time delay potentially involved in
the re-crawl?
I am not saying you haven't solved these problems. Maybe you have --
but if so, then you have (IMHO) dealt with "huge complexity" :-).
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 27 22:13:00 2005