Whenever I look at git log‘s man page I get sad. In mercurial almost all of git log’s options are covered by the revset and template system. These systems are general enough that they can be used for lots of other commands besides hg log. On the whole it’s things like this that make mercurial much easier to use from the command line than git.
Yeah, the forest of options Git has for doing what Mercurial does with revsets and templates makes the already bad CLI design even more painful to live with. At least the rest of the documentation would be easier to browse if they had similar systems in place.
I feel like “the good parts” may be apt in cases where there’s a lot that isn’t good about the thing in question – such as in the case of Crockford’s famously-titled book on jervascrupt. Is that somehow the case with git log?
Whenever I look at
git log‘s man page I get sad. In mercurial almost all of git log’s options are covered by the revset and template system. These systems are general enough that they can be used for lots of other commands besideshg log. On the whole it’s things like this that make mercurial much easier to use from the command line than git.Yeah, the forest of options Git has for doing what Mercurial does with revsets and templates makes the already bad CLI design even more painful to live with. At least the rest of the documentation would be easier to browse if they had similar systems in place.
I feel like “the good parts” may be apt in cases where there’s a lot that isn’t good about the thing in question – such as in the case of Crockford’s famously-titled book on jervascrupt. Is that somehow the case with
git log?Depends on whether you consider the less penetrable parts of the man page to be bad. Readers that don’t probably won’t be interested in the post.