Live data from Hacker News

Gitbox - Everyday git [Mac OS X] interface for human beings

gitbox.pierlis.com

51–53 of 53 posts

Re: Gitbox - Everyday git [Mac OS X] interface for human beings

#51
post #15

Earlier quoted context omitted.

I love the cheat gem. sudo gem install cheat Then do : cheat git A great shortcut to all of the common git command sequences.

sweet didn't know about it, it's very handy with my little Mac OS X alias to open preview from command line : alias preview='groff -Tps > /tmp/tmp.ps && open -a Preview /tmp/tmp.ps' So you can do : cheat git | preview

Nice, very cool alias. Thank-you!

P.S. As an added note, there are TONS of cheat sheets out there. Just do a 'cheat sheets' from the command line and you'll get the all listed. Some of the more common ones I would suspect in the HN community are :

cheat svn

cheat rails

cheat named_scope

cheat curl

cheat blueprint

cheat bash

cheat mysql

cheat ruby

Re: Gitbox - Everyday git [Mac OS X] interface for human beings

#52
post #33

I think it's very possible that these pretty wrappers allow people to hobble along with little to no understanding of how git actually works. If that's the only way that you'll use version control, it's better than nothing. On the other hand, I heartily endorse actually learning how the git model works -- it's not too bad, I promise! . Good places to start: [1] Peepcode's "Git Internals" PDF - $9 - short, sweet, to t…

I find that committing parts of a file in GitX is much easier than using interactive mode in the terminal. That's not a question of understanding the git model, it's just choosing the best tool for the job.

I completely agree. For many tasks the command line sequence of add, commit, push may be sufficient, but sometimes I don't care to wade through my editor merging and selecting portions of diffs to commit. The GitX interface is much more usable in that instance.

Re: Gitbox - Everyday git [Mac OS X] interface for human beings

#53

I think it's very possible that these pretty wrappers allow people to hobble along with little to no understanding of how git actually works. If that's the only way that you'll use version control, it's better than nothing. On the other hand, I heartily endorse actually learning how the git model works -- it's not too bad, I promise! . Good places to start: [1] Peepcode's "Git Internals" PDF - $9 - short, sweet, to t…

not everyone needs to understand how git works. In a couple of projects I work on, for instance, there are webdesigners who NEVER touch code and never used any sort of VCS before (and no, they DO NOT need to learn it) - making it simpler for them to use git is a big win for everyone in the project :-)
Post reply on HN