SVN Status Command Line in 1.8 vs 1.7

A colleague of mine and I discovered that the location of the working revision (working_rev) in 1.8.3 is different from 1.7.12 . We are both using svn.exe from the TortoiseSVN package on Windows. In 1.7 he gets the following: M 1167395 1164911 FHANDFORD C:\ProgramData\Meditech\MTCM

RE: SVN Status Command Line in 1.8 vs 1.7

Hi, As far as I know the last time we updated the columns for 'svn status' was with Subversion 1.6 when we introduced tree conflicts. But while we do promise 'svn status' output stability within minor releases we don't promise that over minor releases. As project we would r

Re: [SVN Users] SVN Status Command Line in 1.8 vs 1.7

Perhaps use the --XML arg? On Wednesday, March 5, 2014, Forest Handford wrote: > A colleague of mine and I discovered that the location of the working > revision (working_rev) in 1.8.3 is different from 1.7.12 . We are both > using svn.exe from the TortoiseSVN package on Windows. In 1.7 he get

Re: 502 Bad gateway error

On 3/5/14, 8:01 AM, Guido Larrain wrote: > 2014-02-28 8:35 GMT-03:00 Guido Larrain >: > > I'm having issues when i tried to commit some HTML files. i mean, some of > them i can committed without problems, but others when i tried to commit > i'm getting a

Re: [SVN Users] SVN Status Command Line in 1.8 vs 1.7

Matt, That's an interesting proposal. Do you know if there are any pre-existing tools in M-AT that could parse up an XML file for us. Also, is the extra space character there as a place holder for a piece of data that is depreciated in 1.8+. For example the 8 spaces (or is it 9?) betwee