On Sun, Jul 17, 2016 at 12:59 AM, Eric S. Raymond <[email protected]> wrote:
> Looking at it now. Can you bisect and identify the bad commit? I have ended up at: sanjeev@X201wily:~/SRC/ntpsec$ git bisect good 82ffaa70e3f0cebe1cf03294d41dcaa338ca7090 was both good and bad Pulling fresh git clone now -- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane
_______________________________________________ devel mailing list [email protected] http://lists.ntpsec.org/mailman/listinfo/devel
