Re: [PATCH 1 of 4] runtests: add a function to test if IPv6 is available

On Wed, Feb 15, 2017 at 06:57:37PM -0800, Jun Wu wrote: > Excerpts from Augie Fackler's message of 2017-02-15 21:32:38 -0500: > > On Wed, Feb 15, 2017 at 06:26:11PM -0800, Jun Wu wrote: > > > Excerpts from Augie Fackler's message of 2017-02-15 21:23:37 -0500: > > > > I'm not overjoyed at the

Re: [PATCH 1 of 4] runtests: add a function to test if IPv6 is available

Excerpts from Augie Fackler's message of 2017-02-15 21:32:38 -0500: > On Wed, Feb 15, 2017 at 06:26:11PM -0800, Jun Wu wrote: > > Excerpts from Augie Fackler's message of 2017-02-15 21:23:37 -0500: > > > I'm not overjoyed at the static default. Is there a reason to use the > > > static default

Re: [PATCH 1 of 4] runtests: add a function to test if IPv6 is available

On Wed, Feb 15, 2017 at 06:26:11PM -0800, Jun Wu wrote: > Excerpts from Augie Fackler's message of 2017-02-15 21:23:37 -0500: > > I'm not overjoyed at the static default. Is there a reason to use the > > static default instead of checking HGPORT, so that multiple users on a > > single box (such as

Re: [PATCH 1 of 4] runtests: add a function to test if IPv6 is available

Excerpts from Augie Fackler's message of 2017-02-15 21:23:37 -0500: > I'm not overjoyed at the static default. Is there a reason to use the > static default instead of checking HGPORT, so that multiple users on a > single box (such as the big compile farm machine several of us favor) > can run the

Re: [PATCH 1 of 4] runtests: add a function to test if IPv6 is available

On Wed, Feb 15, 2017 at 04:50:14PM -0800, Jun Wu wrote: > # HG changeset patch > # User Jun Wu > # Date 1487204311 28800 > # Wed Feb 15 16:18:31 2017 -0800 > # Node ID a70fa1e0fcdb11980338d72dde33dfe047bda7c2 > # Parent e5363cb96233861fc99f7e9b85d7884d3121558c > # Available At