Great suggestion, Jonathan. I've never used bisect (still migrating myself over to the git world), but I'll check out bisect and see if I can track down this bug.
On Fri, Jun 21, 2013 at 4:40 PM, Johnathan Corgan <johnat...@corganlabs.com> wrote: > On Fri, Jun 21, 2013 at 1:36 PM, George Nychis <gnyc...@gmail.com> wrote: > >> >> I'm still trying to track this down to an exact commit that breaks >> this, but I know so far that the GUIs were not broken as of this >> commit: >> >> >> http://gnuradio.org/cgit/gnuradio.git/commit/?id=http://gnuradio.org/cgit/gnuradio.git/commit/?id=81cba98cb1a3adec261aa6b510ee152c3a24bb0d >> >> Trying to divide and conquer with a little bit of intelligence in what >> was committed... > > > Using git bisect is the best way I've found to discover these things; it > takes the guesswork out and scales O(log(n)) in the number of commits > between good and bad versions. > > > -- > Johnathan Corgan > Corgan Labs - SDR Training and Development Services > http://corganlabs.com _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
