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

Re: svn status enhancement

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-08-05 07:26:48 CEST

Scott Palmer <scott.palmer@2connected.org> writes:

> I identified two places that seemed to be where the modifications are
> required. In externals.c the method svn_client__do_external_status
> (), and in status.c: svn_client_status2()

First, sorry for not mailing earlier and saving you the investigative
trip into libsvn_wc (from whence many never return). But
unfortunately, I think neither of these is correct. Your goal is to
eliminate some output, but you need to do this without eliminating
data other users of libsvn_client might actually (continue to) want.

To do this correctly, you need to get your status callback and your
notification callback talking to each other. I'm thinking you could
do this by making the notification baton semi-public and putting a
pointer to it in the status callback baton. With creative use of
booleans and logic, you should be able to choreograph the exotic dance
needed to solve the problem you aim to solve.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 5 07:29:44 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.