News for hackers. Stuff that matters.

A comment on Git manpage generator. Parent comment

Re:Git manpage generator by edwintorok on Thursday April 10, 2014 @01:28PM (#7568122)
What matters is that 'git bisect' helps you find the bug in a significantly smaller number of steps than trying all revisions by hand. The manpage should definitely either mention the algorithm (binary search), or the reason why you would use it in the first place (it significantly reduces the number of steps until you find a bug, versus trying all commits). Note that the 'hg bisect' still fits this requirement, because its name hints at the algorithm.

If it only mentioned that it finds the changeset introducing a bug, without saying how, or that it does it efficiently what would be the reason to use the command at all?

[ Parent | on HN ]
Re:Git manpage generator by Xylakant on Thursday April 10, 2014 @04:14PM (#7569385)
Well, why not say "finds the rev in which a bug was introduces in an efficient way." Why bother me with further details? I don't care how - if the git team finds a better way to do it, fine.

A lot of potential git users won't be aware that binary search is what you want. You just lost those.

[ Parent | on HN ]