Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You have a couple issues here:</p> <ol> <li>You have multiple people sharing a single working copy. This is a bad idea. When you do this, it's too easy for people to step on each others' changes and commit things that aren't ready to be committed. You've lost all accountability - who changed what? Everyone's working on the same files, so now it's impossible to know who did what. Each person should have their own working copy, on their own workstation (or under their own home directory, if you have to work on a remote system).</li> <li>Addendum to the above point: your commit messages describe why you made the change you're committing. If everyone's sharing a working copy, and only one person committing, how are you recording your change history (the "why"s)?</li> <li>You have people not properly using the tools. If you're in a working copy, everything has to be done with <code>svn</code> subcommands. Full stop.</li> <li>You're checking out daily? There's no need for that in a proper Subversion workflow.</li> </ol> <p>To answer the core question: Use <code>svn st -u</code> to look for any changes locally or on the server. It's a good practice to run <code>svn update</code> frequently to pick up changes as soon as possible to prevent problems like this, and commit directory structure changes as soon as possible after making them (assuming it doesn't break something else) so that everyone is aware of the changes.</p> <p>But there is no substitute for good communication between team members and using the tools properly.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload