Originally developed to replace a similar (but commercial) tool called bitkeeper, git was initially developed by Linus Torvalds as a distributed source control tool for the Linux kernel source code. It kind of follows that if it can handle the Linux kernel source code, it can probably handle your project.
Source control (rigorously tracking every change made to a body of source code so that you can undo anything, or develop alternate versions (branches) of a project, is not a trivial exercise, and git is easy to use compared to CVS, subversion, or perforce, but not easy to use the way, say, iPhoto is easy to use.
That said, git is project (or directory) -centric rather than file-centric, meaning its underlying philosophy is radically different from traditional tools. (Simply put, it operates on directories (and all their contents) in much the same way that CVS et al work on files. It turns out that this approach is radically simpler and more effective for most tasks than the traditional approach.
That said, you can install git on almost any machine very quickly, have a (single user) repository for a project set up within minutes, and be committing changes, making branches, and merging branches within an hour. If you've ever used CVS, subversion, or perforce before, you'll be impressed by this statement and probably think I'm exaggerating. Try it and see.