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

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

From: Adam Contardo <acontardo_at_meditech.com>
Date: Wed, 5 Mar 2014 17:06:25 -0500

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?) between the M and the revision number are a set of flags (1 char per
flag) representing things like lock info, whether or not there are newer
revisions on the server, etc? I'm just curious if that space char
represented a piece of data that is no longer relevant in 1.8

On Wed, Mar 5, 2014 at 9:52 AM, Matt McCullough <
matt_mccullough_at_meditech.com> wrote:

> Perhaps use the --XML arg?
>
>
> On Wednesday, March 5, 2014, Forest Handford <fhandford_at_meditech.com>
> 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 gets the
>> following:
>>
>> M 1167395 1164911 FHANDFORD
>> C:\ProgramData\Meditech\MTCM.Universe\MTCM.DEVF.Ring\!AllUsers\Sys\PgmCache\Ring\PgmSource\Foc\FocZ.Subversion.C.focus
>>
>> In 1.8 I get:
>>
>> M 1167395 1164911 FHANDFORD FocZ.Subversion.C.focus
>>
>>
>> C:\ProgramData\MEDITECH\MTCM.Universe\MTCM.DEVF.Ring\!AllUsers\Sys\PgmCache\Ring
>>
>> Notice how in 1.8 working_rev is one character further left. I took a
>> peak at
>> http://svn.apache.org/viewvc/subversion/trunk/subversion/svn/status.c?view=markupin various revisions since march 2013. The svn_cmdline_printf() call in
>> print_status() appears to be consistent. working_rev also seems to be
>> consistently set using apr_psprintf(pool, "%ld", status->revision). We
>> can parse it correctly with either position, but worry that the position
>> may arbitrarily change in the future causing future parsing to fail. As an
>> example, if it moved yet another space to the left, we would lose the left
>> most digit. Any ideas?
>>
>> Thanks,
>> Forest
>> --
>> Forest Handford, Supervisor Development, 781-774-5148
>> Medical Information Technology, Inc.
>> Mailstop: S4W186W, MEDITECH Circle, Westwood, MA 02090
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "SVN Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to svn-users-group+unsubscribe_at_meditech.com.
>> Visit this group at
>> http://groups.google.com/a/meditech.com/group/svn-users-group/.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "SVN Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to svn-users-group+unsubscribe_at_meditech.com.
> Visit this group at
> http://groups.google.com/a/meditech.com/group/svn-users-group/.
>

-- 
Adam Contardo, Programmer Development, 781-774-5161
Medical Information Technology, Inc.
Mailstop: F3N244, MEDITECH Circle, Westwood, MA 02090
Received on 2014-03-06 06:54:49 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.