4 ms·
Part of this has to be a Git vs SVN. (I know that Google Code supports Mercurial, but I believe all project I'm subscribed to use SVN.) But I commit and push w
by pkaler 17y ago
Part of this has to be a Git vs SVN. (I know that Google Code supports Mercurial, but I believe all project I'm subscribed to use SVN.) But I commit and push way more with Git than I did with SVN. Probably twice as often. I usually commit every time I write a function or even a loop. I usually push whenever I've fixed a case in the bug tracker.
With SVN, I used to only commit once I fixed a case.
- schacon 17y agoReally? I do the opposite. You can't commit at all without hitting the server in SVN, where I can go for quite a while in Git without pushing. I would assume that most people would push in Git much less often then committing in SVN. It's obvious that because the commits are faster, they would commit more - and they are (109,000 Git commits over 33,154 pushes vs 17,000 svn commits). So in Git people commit on average 3 times before they contact the server.
- paulbaumgart 17y agoPushing to a public repository (especially forks of ones people actually care about, but this is true in general) gives me a small feeling of accomplishment. It's a way of sharing that I did something I think is useful, especially since it shows up in the news feed of my (handful of) followers. So yeah, I probably push more often than is strictly necessary.