[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: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-01-06 15:33:16 CET

On Wed, 5 Jan 2005, Ben Collins-Sussman wrote:

> On Jan 5, 2005, at 7:30 PM, Philip Martin wrote:
> > "Max Bowsher" <maxb@ukf.net> writes:
> >
> >> Philip Martin wrote:
> >> 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.
> >
> Well, here's an argument for adding a new column (instead of a new
> line): I think it's much more readable to have exactly one line per
> path. Right now, we only violate that rule when there's a replacement:
I just added a column with "K" for locK removed. And a few more columns so
we can avoid this in the future.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 6 15:46:21 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.