Re: Output of svn co - what does E mean?

svn help update has it.

  For each updated item a line will start with a character reporting the
  action taken. These characters have the following meaning:

    A Added
    D Deleted
    U Updated
    C Conflict
    G Merged
    E Existed

  A character in the first column signifies an update to the actual file,
  while updates to the file's properties are shown in the second column.
  A 'B' in the third column signifies that the lock for the file has
  been broken or stolen.

  If --force is used, unversioned obstructing paths in the working
  copy do not automatically cause a failure if the update attempts to
  add the same path. If the obstructing path is the same type (file
  or directory) as the corresponding path in the repository it becomes
  versioned but its contents are left 'as-is' in the working copy.
  This means that an obstructing directory's unversioned children may
  also obstruct and become versioned. For files, any content differences
  between the obstruction and the repository are treated like a local
  modification to the working copy. All properties from the repository
  are applied to the obstructing path. Obstructing paths are reported
  in the first column with code 'E'.

On Tue, Dec 9, 2008 at 12:15 PM, Andy Levy <andy.levy_at_gmail.com> wrote:
> On Tue, Dec 9, 2008 at 10:00, Mark Phippard <markphip_at_gmail.com> wrote:
>> On Tue, Dec 9, 2008 at 9:56 AM, Andy Levy <andy.levy_at_gmail.com> wrote:
>>> I just did the following on a server:
>>>
>>> svn co <URL> --force --username USER --password PASS .
>>>
>>> I was in a directory that already had contents that had, at one time,
>>> come from <URL> but it was not a WC yet (my goal was to get everything
>>> from the URL and then just be able to svn up in the future).
>>>
>>> The output of svn co showed an E in the first column for many files
>>> during the checkout. I can't find a reference to this "status" in the
>>> help for co or st. What does it mean?
>>
>> This is a new feature in 1.5. It stands for 'E'xists. Prior to 1.5
>> the command would have failed if files existed. Now, it leaves those
>> files in place and "slides" the working copy underneath. You should
>> be able to run svn st and see if there are differences and you could
>> then revert or commit.
>
> We've since trashed the WC and checked out fresh, due to non-SVN
> issues with how the code was installed on the server a while back. But
> this explanation does help and makes sense int he context of what I
> saw.
>
> Is this documented somewhere? I didn't see it in the manual or svn help.
>

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=981764
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].