5 ms·

So essentially, its git at work. If you're using svn, then each and every commit of yours gets pushed to the main repository. That, is not feasible if you're wo

So essentially, its git at work. If you're using svn, then each and every commit of yours gets pushed to the main repository. That, is not feasible if you're working on a big feature. With git, you can just continue working on your local machine, and push a series of commits at once. Thats really nifty, for you to "code fearlessly", especially (or maybe only so) if you've got huge changesets. :-)

SoftwareMaven 16y ago
I've been doing this since long before git was a twinkle in Linus' eye. The tools may make it easier or harder, but the attitude is all inside the programmer. Of course, while I'm happy to code fearlessly (there has never been a code module I've been afraid to jump into), it scares me to death to see some others do it. "Hmm, maybe Hank should just take baby steps..."
- spc476 16y ago
  git makes it painless. At work, we use svn, which I've found makes it harder to try those crazy ideas, so I don't even bother (or if I do, I have to checkout the entire project in another directory, which takes forever due to the sheer size of the project, so again, I'm relunctant to do even that).
  - mcantor 16y ago
    You can also do a server-side svn copy to create a branch of trunk (which is relatively instantaneous), then use svn switch to selectively swap out the directories in your working copy relevant to your change. I usually wrap this up in small bash scripts at the root directory that "toggle" the switches. I call it "poor man's dvcs."
  - bostonvaulter2 16y ago
    Have you tried git-svn? The initial checkout can take a while, but it gives you many of the features of git, while still using svn.