Sanjeev Gupta <gha...@gmail.com>:
> On Tue, Jan 26, 2016 at 11:41 PM, Eric S. Raymond <e...@thyrsus.com> wrote:
>
> > OK, here's where you gain a level in hackery. :-)
> >
> > Learn how to perform a git bisection (using Google to find a HOWTO) and
> > nail down which commit broke the lookup. Konowing that, it should be
> > easy to fix.
> >
>
> Eric, I thought the whole point of my using Open Source was that I
> complain, and you et al fix? :-)
Well, yes, often. But...and I'm being serious now...it's good form to
send a request for bisection back to the bug reporter when you suspect
that the bug might be sensitive to environmental factors that are
tricky to identify and replicate. That way you avoid getting ratholed
by an inability to reproduce the bug locally.
(And you *always* suspect tricky environmental factors when DNS lookups
are involved. That is, if you weren't born yesterday.)
Besides, I didn't think you'd *mind* an easy level gain in hackery. :-)
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
