←back to thread

1062 points mixto | 1 comments | | HN request time: 0.211s | source
Show context
scrapcode ◴[] No.42942555[source]

I can't help but feel that Git has completely missed the forest through the trees that you can make a 30+ part guide explaining how to use it.

replies(6): >>42942641 #>>42942672 #>>42942768 #>>42943372 #>>42950299 #>>42954886 #
verandaguy ◴[] No.42942672[source]

Eh, yes and no.

Git porcelain stuff's plenty good for probably 95% of users. `rebase -i` comes with a guide on which commands do what, and you could write a couple of paragraphs about how to format `git log`'s output with your own preferences and tradeoffs -- and porcelain usually includes stuff as eclectic as `git gc`, `git fsck`, and `git rev-parse` by most accounts.

Git plumbing's definitely a bit more obscure, and does a bunch of stuff on its own that you can't always easily do with porcelain commands because they're optimized for the common use cases.

TL;DR: while Git's big (huge even), a lot of what it provides is way off the beaten path for most devs.

replies(2): >>42942997 #>>42946334 #
1. rtldg ◴[] No.42946334[source]

With 'gitk' I'm not sure I'll ever have to learn how to use 'git log'. A Good Enough preinstalled GUI is too convenient