??? 01/06/12 17:30 Read: times Msg Score: +2 +2 Good Answer/Helpful |
#185353 - repo vs working copy Responding to: ???'s previous message |
Jez Smith said:
Don't try to use a networked drive as your suppository, it will be pig slow because.....because of complex networky stuff and the way SVN works Jez, I think you're saying that you don't want to keep your working copy on the network. The repository should be on the network, and you should check out a working copy to wherever you do your work. (I have checked out working copies onto network shares, and while, yes, there can be penalties involved, those have nothing to do with the SCC and everything to do with how an application deals with the data on which it works.) Important point: The working copy should be yours and yours alone. Anyone else working on the same project should check out his/her own working copy. The whole point of a proper revision system is that it handles that sort of bog-standard practice. Of course, it is incumbent on the users to commit changes when necessary, and to also update working copies regularly if others are working on the same thing. -a |
Topic | Author | Date |
SubVersion/Altium/ISO9000 | 01/01/70 00:00 | |
You don't need an admin but it helps | 01/01/70 00:00 | |
Subversion | 01/01/70 00:00 | |
redmine | 01/01/70 00:00 | |
Cheap.. | 01/01/70 00:00 | |
you don't need an admin for svn, but | 01/01/70 00:00 | |
I forgot, most importantly | 01/01/70 00:00 | |
No network? | 01/01/70 00:00 | |
repo vs working copy | 01/01/70 00:00 | |
Training notes | 01/01/70 00:00 | |
??? Surely not | 01/01/70 00:00 | |
subversion | 01/01/70 00:00 | |
What Subversion does for you | 01/01/70 00:00 | |
What he said! | 01/01/70 00:00 | |
git | 01/01/70 00:00 | |
Bad name | 01/01/70 00:00 |