[administrivia: added people involved in the main discussion thread back
on CC line, and also added CCouder who seems to be fond of the command]
Michal Vyskocil <mvyskocil@xxxxxxx> writes:
> The bugfix command works like the previous git bisect start --reverse.
Does any released version of git have "bisect start --reverse"?
$ git bisect start --reverse
unrecognised option: '--reverse'
Let's suppose that we had a "git frotz" Porcelain subcommand, that used to
say "xyzzy" when all is well, but says "nitfol" these days. I released a
(bad) script that parses the output from the subcommand, and want to say
something like "This script only works with Git version after X", and to
find out the value of X, I need to bisect the history to find when "frotz"
started to say "nitfol".
I am not trying to find a commit that introduced a bug/regression to cause
the recent "frotz" to say "nitfol". Neither am I trying to find a fix that
corrected the earlier bogus output "xyzzy". No value judgement is involved
in this scenario.
I wonder if something along the following line would make the usage more
pleasant and self-explanatory:
$ git bisect start --used-to='git frotz says xyzzy' v0.99 master
Bisecting: 171 revisions left to test after this (roughly 8 steps)
$ ... build and then test ...
$ git bisect tested
You are trying to check: git frotz says xyzzy
Does the result satisify what you are trying to find [y/n]? yes
Saying 'yes' would be like saying 'good' and 'no' would be like saying
'bad' here.
When trying to find regression, you would say:
$ git bisect start --used-to='it works' v0.99 master
and you say 'yes' if it works (equivalent to 'good'), and 'no' if it does
not (equivalent to 'bad').
When trying to find a fix, you would say:
$ git bisect start --used-to='checkout $tree $path clobbers $path' v0.99 master
and you say 'yes' if it is still broken at the tested version (equivalent
to your reversed 'good'), and 'no' if the tested version contains a fix
(equivalent to your reversed 'bad').
I am not married to the name of the option, but --used-to='...' felt more
or less self-explanatory name to signal users what to describe in that
text. The condition "You are trying to check:" cue wants to remind the
user is "we used to do *this* but now we don't", and the command is trying
to see when it changed.
Thoughts?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html