> > prepping for delivering upcoming git courses, and i'm adding a short > > page for questions i get on a regular basis along the lines of "how do > > you do X in git?" when, for the most part, i typically answer, "why > > would you want to do that in the first place?" > > Like maybe locking a file on checkout? Git doesn't lock files, mandatory locking may be on its way out from the kernel, and the concept doesn't even apply because it's a DVCS. It sure as heck would never scale. Try that on the kernel! Waaaaaay too many contributors. There is no such thing as telling others you have a lock on a file, much less doing so on your own machine. Do your changes, then push, format-patch, etc., and deal with the conflicts, rather than proactively refusing access to everybody else. Also, checking out a file is just that, putting the snapshot of the file from commit X in the working tree (and also staging it). It's nowhere near like in horrors like SharePoint.