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

Re: [Locking] svn up output

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2005-01-06 02:30:09 CET

"Max Bowsher" <maxb@ukf.net> writes:

> Philip Martin wrote:
>> "Peter N. Lundblad" <peter@famlundblad.se> writes:
>>> I don't want to use the third column. One possibility is to write
>>> something on the next line like:
>>> U path
>>> Lock remvoed.
>>> path2
>>> Lock removed.
>> It's inconvenient for a script to have to parse multiple lines like
>> that. How about
>> U path
>> B path
>> U path2
>> S path2
> But, lock-changes are not text-changes. What if there are both to report?

My example above reports both.

> I think we *need* to add another column.

I think we have to add a column or a line.

> Yes, it will break some scripts, but really, *anything* we change will
> break some scripts, and we absolutely *must* show lock changes in
> update output.

Some scripts will break if we add a column, some will break if we add
a line, but if we add a line then only people using locks will see
anything change.

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 6 02:31:23 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.