News for hackers. Stuff that matters.
Re:Torvalds: git vs CVS by sshumaker on Friday April 16, 2010 @07:55PM (#1272281)
With binary files, you really want an explicit checkout (exclusive lock) system - since there's typically no way to merge them. This makes the commit/merge style SCSes a bad fit for binary assets (and partially explains the popularity of Perforce, which is a lock-based SCS).
Re:Torvalds: git vs CVS by dalore on Friday April 16, 2010 @08:56PM (#1272364)
That and Perforce is a commercial company that provides support with their product. By default perforce doesn't lock, but it knows when a user has a file checked out for "edit".

By default all files are set read only. This was a big downside when you had no internet connection.

Re:Torvalds: git vs CVS by koenigdavidmj on Saturday April 17, 2010 @03:17AM (#1272750)
Yeah, but 'chmod u+w filename' and you're back in business. The GUI has a "resolve offline work" feature that will find everything.

Of course, if you don't mark it writable (and just use :w! in Vim, for instance), then a 'p4 sync' may eat your work if anyone's changed the file.

Re:Torvalds: git vs CVS by dalore on Monday April 26, 2010 @06:43AM (#1294553)
Ahh the resolve offline work feature must be new. It wasn't around when I was using perforce.
Re:Torvalds: git vs CVS by koenigdavidmj on Monday April 26, 2010 @10:41PM (#1297026)
Sadly, it has no direct CLI equivalent. You may find http://p4delta.sourceforge.net/ useful, however; it's like `svn up` for Perforce.