If it's only for backup or transport purposes, you could still rsync the
repository to your mobile. Making it a bare repository would reduce the size
of stuff to be rsynced.
I'm not familiar with the internals <http://progit.org/book/ch9-6.html> of a
git push or pull, but there is a lot of consistency checking going on,
checking that none of the objects in either repository have become
corrupted. I noticed this today when a colleague was just pushing a new
branch into a remote repository. The branch had only diverged a few commits
away from an existing branch, but still it took many minutes of "uploading"
for the branch to get created on the remote.
If you're looking for some real git developers, you're better of asking on
the real mailing list: http://vger.kernel.org/vger-lists.html#git
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at