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

Re: status output and long fields

From: <cmpilato_at_collab.net>
Date: 2003-02-19 19:29:05 CET

Karl Fogel <kfogel@newton.ch.collab.net> writes:

> cmpilato@collab.net writes:
> > That's fine. I think I'm gonna go with auto-sizing columns with
> > minimum widths and a header line. That way, a script can always read
> > the first line of output, hack it up to determine each column's
> > starting offset, and then go from there.
> >
> > If anyone objects, speak now.
> Doesn't this make it impossible to output status streamily? You'd
> have to have all the data before you can print out anything...

We don't do it streamily today. See svn_cl__print_status_list. Yes,
this would prevent us from moving to a streamy output. But keep in
mind that these changes would be *entirely* in the cmdline client --
if the underlying svn_client_status() code switched to a streamy
interface, only the cmdline client would miss out.

As it turns out, the presence of the -u status option makes
streaminess almost impossible anyway, since we have to make a pass
over the working copy, and then amend that information with a separate
chunk of data from the server.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 19 19:30:40 2003

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