[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: SteveKing <steveking_at_gmx.ch>
Date: 2005-05-20 19:10:10 CEST

John Peacock wrote:
> steveking wrote:

>> But there's another way to go here:
>> - have a log message template stored somewhere in the working copy
>> (inherited property, normal property, ...) which a client can use.
> Obviously I'm in favor of this... :-)
>> - that property can either be a complete log message template, or have
>> a special value which indicates that the repository has to be contacted.
>> - That special value also indicates if the change-files-list has to be
>> sent to the server or not
> I'm not opposed to this, but I'm also not sure that it's necessary
> either. We shouldn't get too caught up in the possibly obscure edge
> case to see that we can get 90+% of the cases simply and without making
> the last 10% completely impossible.

I'm not sure what you mean with the 90/10 percent here. All I'm asking
for is to have the option to *not* force a client to contact the
repository. Especially if the hook script there just returns a static
template or worse: nothing! If there's even a chance to avoid a repo
roundtrip, we should take it. There's absolutely no reason to make it
impossible for clients to optimize/work-around existing performance


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 20 19:13:29 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.