On 10/31/06, Bill Kelly <billk / cts.com> wrote:
> Interesting.  The kind of Communication I remember as the
> staple of locking-style VC projects went something like this:
> "Bob, I need access to frobozz.cpp, will you be checking in
> soon?"  "Well, I haven't changed frobozz very much, but if I
> check it in it won't compile for you. I can't check it in until
> I finish with XYZZY, then I'll check in all these files at once."
> "Oh... well I guess I'll just modify my copy locally and merge
> manually, as usual."
>
> I *never* want to go back to that.  Maybe this isn't so much
> of an issue with p4, since it apparently _does_ know how to
> merge changes?  (The old locking-style VC systems I used didn't
> know about merging at all.)

It isn't an issue with p4. We use it at work. Even if Perforce didn't
offer free licenses for open source work, it's worth every freakin'
penny.

-austin
-- 
Austin Ziegler * halostatue / gmail.com * http://www.halostatue.ca/
               * austin / halostatue.ca * http://www.halostatue.ca/feed/
               * austin / zieglers.ca