Home/ Questions/Q 122351
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T04:06:54+00:00

Let me start by explaining our set-up: I am working with some contractors. They

  • 0

Let me start by explaining our set-up:

I am working with some contractors. They are using Visual Source Safe for source control and our company is using Subversion. Every few days they preform a checkin to our repository by doing the following steps:

  1. Checkout from our repository (they’re the only ones working on it so this doesn’t actually do anything)
  2. Copy into the directory all the application files
  3. Commit back

Its a horrible process and we plan to address it in the next iteration but it works. Except that sometimes it doesn’t. Sometimes after they do the commit some of the files have a gray checkmark overlay.

I am not sure what this means. Googling around implies it might have something to do with locking but nobody is explicitly locking anything! The files seem to get committed, but they are missing when I do a check out. I am sure that I am missing something.

Can anyone explain whats gong on and how to fix it?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. from here:

    If you have set the svn:needs-lock property on a file, Subversion makes that file ReadOnly until you get a lock on that file. Read-only files have this overlay to indicate that you have to get a lock first before you can edit that file.

    We don’t use the needs-lock stuff here, so I can’t really explain more. It’s a start though.

    Edit: Since they are using VSS, the files will have the read-only attribute set when they are not checked out. TortoiseSVN may be interpreting this as having the needs-lock set.

    • 0