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

2014-03-05 Thread Matt McCullough
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: [SVN Users] SVN Status Command Line in 1.8 vs 1.7

2014-03-05 Thread Adam Contardo
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

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

2014-03-06 Thread Bert Huijben
recommendation still stands) Bert From: Adam Contardo [mailto:aconta...@meditech.com] Sent: woensdag 5 maart 2014 23:06 To: Matt McCullough Cc: Forest Handford; users@subversion.apache.org; David T. Murphy; SVN Users Subject: Re: [SVN Users] SVN Status Command Line in 1.8 vs 1.7

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

2014-03-07 Thread Forest Handford
- > > ]] > > > > If I read this correctly this should only change the output for revision > numbers over 6 digits. (Of course the --xml recommendation still stands) > > > > Bert > > > > *From:* Adam Contard

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

2014-03-07 Thread Adam Contardo
atus), >> >> status->wc_is_locked ? 'L' : ' ', >> >> >> >> >> >> ]] >> >> >> >> If I read this cor