On Mon, Apr 27, 2009 at 06:55:38PM -0400, John Dlugosz wrote: > I'm interested in finding out how people use git "on the side", when it > is not the project's actual version control system. Thomas already mentioned using "git diff" separate from a git repository; I find that "git diff --color-words" is much nicer than "wdiff", which does something similar (though I rarely use it outside of a repo only because I put _everything_ into git :) ). One of the nice things about git (and other distributed VCS's) is that creating a repo is very lightweight. If I am going to write a patch for some other software, the first thing I'll do after untarring it is "git init; git add .; git commit -m import". So it kind of blurs the concept of "what is the project's actual version control system" as you wrote above. If you consider the project to be my patch, it _is_ the VCS. Even though upstream may not be using it. And of course, if I am going to do multiple patches, then I may convert and track upstream's history via git. If you are looking for exotic uses of git, you may be interested in Dscho's "Using Git For What It Is Not Intended" contest: http://search.gmane.org/?query=UGFWIINI -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html