It’s as though every other version control system I've ever used was created by people who were really into version control and Git was created by people who were really into hacking.
Fork me!
If you move the slides quickly, it feels a bit like playing Desktop Tower Defense.
Justin French: alias push?='git cherry -v origin' — beautiful.
Interesting thread wherein Linus describes the need for various types of Git workflows for leaf developers vs. maintainers. Lot’s of talk about the pros and cons of rebasing in different situations.
Oliver Steele details his (and others’s) Git workflow with a bunch of illustrative graphs, emphasizing one of my favorite aspects of Git: There’s More Than One Way To Do It.
A gem for your project is automatically built each time the project_name.gemspec file is changed on your master branch.
All manners of good stuff here.
Now this is the kind of direction I hope to see GitHub and Gitorious go in the future.
A nice solution to “The Tangled Working Copy Problem” for VCS’s that don’t allow you to pluck out portions of a working copy to commit. Allows editing the diff that’s about to be committed.
There are some great tips for owning your local workflow in here.
I can’t say whether this is an accurate description of hg but he nails a lot of the things that makes git interesting, IMO.
I'm a bzr refugee in Git-land, myself.
Bill de hÓra gives some reasons for using a distributed VCS even when the downstream repo is non-distributed.
Okay, I've read about five of these articles purporting to explain Git’s internal conceptual framework. This was the first that really made things click in any significant way.
More praise for GitHub from a small team of Django hackers that built a site in three hours on one night with a little help from git…
A quick script I threw together to convert simple bzr branches to git repos. Requires git, bzr, and rsync.
“The last features standing get re-integrated into another branch known as the ‘trailer park’ to try to find a new life for themselves. Note that ghetto is frequently called ‘trunk’, and the trailer park something like ‘releng’”
Huge thanks to al3x for the invite. I'll be writing up my experience over the next week or so.
Seriously interesting web based git browser and collaboration tool from the folks at Engine Yard. If anyone has a spare invite laying around, hook me up: rtomayko@gmail.com. I have a bunch of stuff sitting in bzr repos that I'd like to flip over to git.
Finally: “this manual is designed to be readable by someone with basic UNIX command-line skills, but no previous knowledge of git.”
There’s some good questions here. I've been running into a few of the same issues while experimenting with moving some of my bzr projects to git. Can one of the git pros out there have a look?
Wherein Aristotle convinces me to seriously consider moving my experimental bzr projects to git. I've seen the content vs. file tracking argument before but never really understood what the actual impact of this difference was.
“…. But after closely studying Git I'm a little bit awestruck; Torvalds is a frickin' genius, a true visionary, and somehow managed to just "get it” and instantly, in a flash of insight, come up with “the solution” for version control."