@takeshitakenji What do you think `git format-patch` and `git am` are for? Git was written by a guy whose primary project workflow is e-mailed patches. The repository itself is what keeps track of changes and the reasoning.

The point of a version control system is to have a working copy of a given project and its entire history, on the off chance that a decision made 10 commits ago is bad and needs to be reversed.

A distributed one simply gets rid of the primary weakness of SVN and CVS; *anyone* who clones the repo can work on it anywhere, and then submit patches (via e-mail or other means) to others.

Under this model, the best way to get your changes into "the main project" is to talk to the ones who control what's considered the canonical repository and convince them to add it to their repo. Once they do, others pull from them and now everyone has your patch.

If you don't mind me asking, how do you personally use git?