[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: RFC: Log Message Templates via new hook.

From: John Peacock <jpeacock_at_rowman.com>
Date: 2005-05-20 16:32:27 CEST

Mark Phippard wrote:
> Performance is not related to my point #1. You are correct that is
> related to point #2. Please re-read if necessary. Point #1 is about a
> valid feature that the GUI provides.

OK, you're right. I'm arguing about the asynchronous log entry, which I
thought was the motivation for both #1 and #2. Reading between the
lines now I see that TSVN must be running the equivalent of 'svn status'
when the user goes to commit, then presents a dialogue and allows the
user to deselect file before the actual commit is started. All
perfectly valid uses of the API, but not the way that the CLI uses the
API at all; not wrong but different.

> I think there have been plenty of complaints about the performance of svn
> status on Windows. This is nothing new.

Thus laying the blame firmly on NTFS, where it belongs... ;-)

> I am not vetoing anything. I am simply trying to bring the concerns of
> the GUI's into the design discussion. Certainly those concerns deserve to
> be raised?

Very much so; I am not trying to stifle discussion. I'm just concerned
that the discussion not get into "TSVN does this now and your new
feature breaks it" and rather moves in the direction of "this new
feature is less optimal for TSVN because of X, how can TSVN do things
differently or how can we tweak the original feature to make it easier
for TSVN to maintain its own feature?"

For example, it would seem worthwhile to have TSVN behave in exactly the
same manner as now. If, during the creation of the execution of the
commit to the repository a custom log-template is required, then TSVN
can pop up a new requester informing the user of the template
requirement and offer to:

a) override the proposed template with the already entered message
b) append the existing message to the end of the proposed template and
give the user the opportunity to revise
c) drop the message and start from scratch

(with 'b' being the most sane default).

I just want to make sure that all the assumptions be considered: on the
part of the GUI authors as well as the CLI users and base API.


John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 20 16:35:03 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.