Branko Čibej <brane@xbc.nu> writes:
> If we add the target URL info to the template (and I'm not opposed to
> that in general), then I'd suggest we show both the local path and the
> URL. That means two lines per file, of course.
I think that's okay. I guess we'd put the URL in parens right below
the local path? Plus we'd probably want a blank line between each
pair, for readability, although that would bring us up to 3x...
When people delete the path block from a log message, they usually
delete it as a block, so doubling or tripling the number of lines
isn't much of a penalty for those who never use the section anyway.
For those who *do* use it, I'm not sure whether local paths or URLs
would be more useful in the common case, but if (for an individual
user) there is an overwhelmingly common case, then the other style of
information would just be a distraction. Thus I find myself on the
brink of venial sin, contemplating adding a config option to control
this:
[helpers]
### Set log-path-list-local-paths to display committable items
### as local working copy paths in the log message template
### created when using editor-cmd, $EDITOR, etc. This can be
### used together with log-path-list-urls; if neither is
### specified, default to local paths.
### Set log-path-list-urls to display committable items as URLs,
### similarly to log-path-list-local-paths.
# log-path-list-local-paths = yes
# log-path-list-urls = no
What do you think, has this gotten out of hand? Should we just do
both styles unconditionally? Stay with status quo? Be *really* fancy
and detect switches & use the both-ways-style in that case, otherwise
defaulting to URLs?
-Karl
--
www.collab.net <> CollabNet | Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 8 21:02:50 2006