On Sun, 2004-02-22 at 12:29, John Beppu wrote: > > One thing: How do we make sure that my changes don't clobber something > > somebody else already worked on the time I work on it? > > Good communication is the key.
Very true. > If svn is anything like cvs on this matter, there's no locking of > files like some other version control systems. Everyone who has > write access to the repository is 'trusted' to do sensible things. Also true. We can revert things if they're severely broken. However, that's a pain, so try not to break them if possible! :) > However, you don't have to chronicle your every little move. For > example, if you need to reformat a few lines of code here and there > or add a few comments, just do it. Run the tests too. > Use your judgement to determine what's noteworthy and what's not. If it's a big change, generate a patch and post it to the list before applying. Also, remember to update before you commit. Spending a few minutes merging -- on those rare occasions where there might be a collision -- will prevent lots of trouble later on. There's trouble every time I forget this. -- c
