suvayu ali <fatkasuvayu+li...@gmail.com> writes: > Hi Jambunathan > > On 29 October 2010 03:17, Jambunathan K <kjambunat...@gmail.com> wrote: >> wish there was a way to say this: >> >> - "do bisection on the revisions where org-latex.el changed (as opposed >> to revisions where HEAD moved)" >> >> The candidate commits then would have reduced to 30 odd commits rather >> than 851 that one had to contend with. >> > > I see in `man git-bisect' a form like this is shown as valid, > > git bisect start [<bad> [<good>...]] [--] [<paths>...] > > Wouldn't that do the job? >
Indeed. One more tools in the armour. ,---- [Example from Git Bisect Manual] | Cutting down bisection by giving more parameters to bisect start | | You can further cut down the number of trials, if you know what | part of the tree is involved in the problem you are tracking | down, by specifying path parameters when issuing the bisect start | command: | | $ git bisect start -- arch/i386 include/asm-i386 `---- Jambunathan K. _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
