Hacker News Reader

Comment by masklinn | Hacker News Reader

Warning: not actually git commands, rather TFAA's aliases for possibly useful combinations of switches and/or commands.

See, switches in git are there because git maintains backward compatibility. Sometimes a switch really would logically be better as a whole new command. But it's a common refrain to hear that git hides useful things in the switches.

This article is a great way to find those hidden things.

> See, switches in git are there because git maintains backward compatibility.

Switches are there because git commands tend to greatly leak the abstraction and group behaviour in terms of the underlying plumbing, and because Git maintainers most likely would rather add new switches to existing commands than new commands intersecting with existing ones.

> Sometimes a switch really would logically be better as a whole new command.

Which could trivially be done without BC issues and thus can't be an explanation why existing commands keep growing new switches.

> This article is a great way to find those hidden things.

It would have been a useful article if it had been about showcasing interesting or useful git switches.

Alternatively, read the documentation and know how to use your tools instead of reading blog posts that lists a few things one person has found useful.

I should really read more of the git doc but at least I learned about aliasing in the gitconfig from this even if, I too, was expecting actual git commands

Yes, the title is misleading.

edit: downvote?

Agreed - these aren't lesser known git commands at all.

The switches given to git commands in the article might be lesser-known, but title could be clearer that this is:

    > Some suggestions for git aliases

TFAA?

The Fucking Article's Author.

Reply on news.ycombinator.com