"Ian Brockbank" <Ian.Brockbank@wolfsonmicro.com> wrote on 09/23/2004
> Hi Mark,
> > A C:/workspaces/dev/developer/tocObjRep.xml
> > A C:/workspaces/dev/developer/tocCheckoutReference.xml
> > 117 C:/workspaces/dev/developer/build.properties
> > 117 C:/workspaces/dev/developer/tocCheckouts.xml
> > 117 C:/workspaces/dev/developer/plugin.xml
> > A C:/workspaces/dev/developer/tocObjRepGettingStarted.xml
> > A C:/workspaces/dev/developer/tocWorklistsProcedures.xml
> > A C:/workspaces/dev/developer/tocObjRepReference.xml
> > A C:/workspaces/dev/developer/tocWorklistsConcepts.xml
> > A C:/workspaces/dev/developer/tocCheckoutProcedures.xml
> > A C:/workspaces/dev/developer/tocPreferences.xml
> > 117 C:/workspaces/dev/developer/tocWorklists.xml
> > A C:/workspaces/dev/developer/tocCheckoutConcepts.xml
> > D C:/workspaces/dev/developer/tocObjectRepository.xml
> > Updated to revision 1864.
> I think it has something to do with what sort of an update it is. If I
> remember right, 103 is a plain update, 117 is an update which causes
> conflict (and I don't know what 170 is - property update?).
Mine are always 117, so that must be the one for "normal". Why wouldn't
they just use the same symbols as svn update?
>From the book:
For each updated item a line will start with a character reporting the
action taken. These characters have the following meaning:
I always assumed it was some sort of character encoding flaw, and the 117
mapped to something.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Thu Sep 23 23:52:47 2004