devel  

Messages by Thread

• • Re: NTS: config and initialization Hal Murray via devel
  • Re: NTS: config and initialization Gary E. Miller via devel
  • Re: NTS: config and initialization Hal Murray via devel
  • Re: NTS: config and initialization Gary E. Miller via devel
  • Re: NTS: config and initialization Hal Murray via devel
  • Re: NTS: config and initialization Gary E. Miller via devel
  • Re: NTS: config and initialization Hal Murray via devel
  • Re: NTS: config and initialization Gary E. Miller via devel
  • Re: NTS: config and initialization Hal Murray via devel
  • Re: NTS: config and initialization Gary E. Miller via devel
  • Re: NTS: config and initialization Daniel Franke via devel
• Tangle - cookie keys file Hal Murray via devel
  • Re: Tangle - cookie keys file James Browning via devel
  • Re: Tangle - cookie keys file Eric S. Raymond via devel
  • Re: Tangle - cookie keys file Richard Laager via devel
  • Re: Tangle - cookie keys file Eric S. Raymond via devel
  • Re: Tangle - cookie keys file Richard Laager via devel
  • Re: Tangle - cookie keys file Gary E. Miller via devel
  • Re: Tangle - cookie keys file Daniel Franke via devel
  • Re: Tangle - cookie keys file Gary E. Miller via devel
  • Re: Tangle - cookie keys file Daniel Franke via devel
  • Re: Tangle - cookie keys file Gary E. Miller via devel
  • Re: Tangle - cookie keys file Hal Murray via devel
  • Re: Tangle - cookie keys file Richard Laager via devel
  • Re: Tangle - cookie keys file Hal Murray via devel
  • Re: Tangle - cookie keys file Gary E. Miller via devel
  • Re: Tangle - cookie keys file Richard Laager via devel
  • Re: Tangle - cookie keys file Gary E. Miller via devel
  • Re: Tangle - cookie keys file Hal Murray via devel
  • Re: Tangle - cookie keys file Richard Laager via devel
  • Re: Tangle - cookie keys file Hal Murray via devel
  • Re: Tangle - cookie keys file Eric S. Raymond via devel
  • Re: Tangle - cookie keys file Hal Murray via devel
  • Re: Tangle - cookie keys file Achim Gratz via devel
  • Re: Tangle - cookie keys file Gary E. Miller via devel
  • Re: Tangle - cookie keys file Eric S. Raymond via devel
  • Re: Tangle - cookie keys file Hal Murray via devel
  • Re: Tangle - cookie keys file Achim Gratz via devel
  • Re: Tangle - cookie keys file Gary E. Miller via devel
  • Re: Tangle - cookie keys file Hal Murray via devel
  • Re: Tangle - cookie keys file Gary E. Miller via devel
  • Re: Tangle - cookie keys file Richard Laager via devel
  • Re: Tangle - cookie keys file Gary E. Miller via devel
  • Re: Tangle - cookie keys file Hal Murray via devel
  • Re: Tangle - cookie keys file Gary E. Miller via devel
  • Re: Tangle - cookie keys file Hal Murray via devel
  • Re: Tangle - cookie keys file Gary E. Miller via devel
  • Re: Tangle - cookie keys file Hal Murray via devel
  • Re: Tangle - cookie keys file Gary E. Miller via devel
  • Re: Tangle - cookie keys file Hal Murray via devel
  • Re: Tangle - cookie keys file Gary E. Miller via devel
• timer_create Hal Murray via devel
  • Re: timer_create Eric S. Raymond via devel
  • Re: timer_create Daniel Franke via devel
• How not to design a wire protocol Eric S. Raymond via devel
  • Re: How not to design a wire protocol Daniel Franke via devel
  • Re: How not to design a wire protocol Eric S. Raymond via devel
  • Re: How not to design a wire protocol Hal Murray via devel
  • Re: How not to design a wire protocol Eric S. Raymond via devel
  • Re: How not to design a wire protocol Hal Murray via devel
  • Re: How not to design a wire protocol Achim Gratz via devel
  • Re: How not to design a wire protocol Richard Laager via devel
  • Re: How not to design a wire protocol Ian Bruene via devel
  • Re: How not to design a wire protocol Gary E. Miller via devel
  • Re: How not to design a wire protocol Daniel Franke via devel
  • Re: How not to design a wire protocol Eric S. Raymond via devel
  • Re: How not to design a wire protocol Daniel Franke via devel
  • Re: How not to design a wire protocol Eric S. Raymond via devel
  • Re: How not to design a wire protocol Daniel Franke via devel
  • Re: How not to design a wire protocol Hal Murray via devel
  • Re: How not to design a wire protocol Daniel Franke via devel
  • Re: How not to design a wire protocol Hal Murray via devel
  • Re: How not to design a wire protocol Daniel Franke via devel
  • Re: How not to design a wire protocol Eric S. Raymond via devel
  • Re: How not to design a wire protocol Hal Murray via devel
  • Re: How not to design a wire protocol Eric S. Raymond via devel
  • Re: How not to design a wire protocol Richard Laager via devel
  • Re: How not to design a wire protocol Gary E. Miller via devel
  • Re: How not to design a wire protocol Richard Laager via devel
  • Re: How not to design a wire protocol Gary E. Miller via devel
  • Re: How not to design a wire protocol Eric S. Raymond via devel
  • microjson vs. libjsmn Eric S. Raymond via devel
• Off topic: Comodo James Browning via devel
  • Re: Off topic: Comodo Gary E. Miller via devel
• Units foo-up Eric S. Raymond via devel
• Re: What's left to doo on NTS. Eric S. Raymond via devel
  • Re: What's left to doo on NTS. Eric S. Raymond via devel
  • Re: What's left to doo on NTS. Hal Murray via devel
  • Re: What's left to doo on NTS. Eric S. Raymond via devel
  • Re: What's left to doo on NTS. Hal Murray via devel
  • Re: What's left to doo on NTS. Eric S. Raymond via devel
  • Re: What's left to doo on NTS. Kurt Roeckx via devel
  • Re: What's left to doo on NTS. Hal Murray via devel
  • Re: What's left to doo on NTS. Kurt Roeckx via devel
  • Re: What's left to doo on NTS. Daniel Franke via devel
  • Re: What's left to doo on NTS. Kurt Roeckx via devel
  • Re: What's left to doo on NTS. Gary E. Miller via devel
  • Re: What's left to doo on NTS. Kurt Roeckx via devel
  • Re: What's left to doo on NTS. Gary E. Miller via devel
  • SO_TIMESTAMP may go away Eric S. Raymond via devel
  • Re: SO_TIMESTAMP may go away Hal Murray via devel
  • Re: SO_TIMESTAMP may go away Eric S. Raymond via devel
  • Re: SO_TIMESTAMP may go away Hal Murray via devel
  • Re: SO_TIMESTAMP may go away Eric S. Raymond via devel
  • Re: SO_TIMESTAMP may go away Daniel Franke via devel
  • Re: SO_TIMESTAMP may go away Hal Murray via devel
  • Re: SO_TIMESTAMP may go away Daniel Franke via devel
  • Re: SO_TIMESTAMP may go away Daniel Franke via devel
  • Re: SO_TIMESTAMP may go away Hal Murray via devel
  • Re: SO_TIMESTAMP may go away Gary E. Miller via devel
  • Re: SO_TIMESTAMP may go away Gary E. Miller via devel
  • Re: SO_TIMESTAMP may go away Eric S. Raymond via devel
  • Re: SO_TIMESTAMP may go away Daniel Franke via devel
  • Re: SO_TIMESTAMP may go away Daniel Franke via devel
  • Re: What's left to doo on NTS. Eric S. Raymond via devel
  • Re: What's left to doo on NTS. Gary E. Miller via devel
  • Re: What's left to doo on NTS. Hal Murray via devel
  • Re: What's left to doo on NTS. Gary E. Miller via devel
• REFCLOCK rises again Eric S. Raymond via devel
  • Re: REFCLOCK rises again Ian Bruene via devel
  • Go winnage (was: Re: REFCLOCK rises again) Eric S. Raymond via devel
  • Re: Go winnage (was: Re: REFCLOCK rises again) Hal Murray via devel
  • Re: Go winnage (was: Re: REFCLOCK rises again) Eric S. Raymond via devel
  • Re: REFCLOCK rises again Hal Murray via devel
  • Re: REFCLOCK rises again Eric S. Raymond via devel
  • Re: REFCLOCK rises again Hal Murray via devel
  • Re: REFCLOCK rises again Eric S. Raymond via devel
  • Re: REFCLOCK rises again Hal Murray via devel
  • Re: REFCLOCK rises again Eric S. Raymond via devel
  • Re: REFCLOCK rises again Hal Murray via devel
  • Re: REFCLOCK rises again Eric S. Raymond via devel
  • Re: REFCLOCK rises again Hal Murray via devel
  • Re: REFCLOCK rises again Eric S. Raymond via devel
  • Re: REFCLOCK rises again Achim Gratz via devel
  • Re: REFCLOCK rises again Eric S. Raymond via devel
  • Re: REFCLOCK rises again Achim Gratz via devel
  • Re: REFCLOCK rises again James Browning via devel
  • Re: REFCLOCK rises again Hal Murray via devel
  • Re: REFCLOCK rises again Achim Gratz via devel
  • Re: REFCLOCK rises again Hal Murray via devel
  • Re: REFCLOCK rises again Gary E. Miller via devel
  • Re: REFCLOCK rises again Gary E. Miller via devel
  • Re: REFCLOCK rises again Richard Laager via devel
  • Re: REFCLOCK rises again Gary E. Miller via devel
  • Re: REFCLOCK rises again Richard Laager via devel
  • Re: REFCLOCK rises again Matthew Selsky via devel
  • Re: REFCLOCK rises again Hal Murray via devel
  • Re: REFCLOCK rises again Hal Murray via devel
  • Re: REFCLOCK rises again Eric S. Raymond via devel
  • Re: REFCLOCK rises again Hal Murray via devel
  • Re: REFCLOCK rises again Hal Murray via devel
  • Re: REFCLOCK rises again Hal Murray via devel
  • Re: REFCLOCK rises again Gary E. Miller via devel
  • Re: REFCLOCK rises again Hal Murray via devel
  • Re: REFCLOCK rises again Gary E. Miller via devel
• Re: What's left to doo on NTS Daniel Franke via devel
  • Re: What's left to doo on NTS Gary E. Miller via devel
  • Re: What's left to doo on NTS Daniel Franke via devel
  • Re: What's left to doo on NTS Achim Gratz via devel
  • Re: What's left to doo on NTS Hal Murray via devel
  • Re: What's left to doo on NTS Achim Gratz via devel
  • Re: What's left to doo on NTS Kurt Roeckx via devel
  • Re: What's left to doo on NTS Achim Gratz via devel
  • Re: What's left to doo on NTS Kurt Roeckx via devel
  • Re: What's left to doo on NTS Achim Gratz via devel
  • Re: What's left to doo on NTS Hal Murray via devel
  • Re: What's left to doo on NTS Hal Murray via devel
  • Re: What's left to doo on NTS Richard Laager via devel
  • Re: What's left to doo on NTS Hal Murray via devel
  • Re: What's left to doo on NTS Daniel Franke via devel
  • Re: What's left to doo on NTS Hal Murray via devel
  • Re: What's left to doo on NTS Achim Gratz via devel
  • Re: What's left to doo on NTS Hal Murray via devel
  • Re: What's left to doo on NTS Daniel Franke via devel
  • Re: What's left to doo on NTS Achim Gratz via devel
  • Re: What's left to doo on NTS Daniel Franke via devel
  • Re: What's left to doo on NTS Gary E. Miller via devel
  • Re: What's left to doo on NTS Daniel Franke via devel
  • Re: What's left to doo on NTS Gary E. Miller via devel
  • Re: What's left to doo on NTS Achim Gratz via devel
  • Re: What's left to doo on NTS Achim Gratz via devel
  • Re: What's left to doo on NTS Hal Murray via devel
  • Re: What's left to doo on NTS Achim Gratz via devel
  • Re: What's left to doo on NTS Gary E. Miller via devel
  • Re: What's left to doo on NTS Eric S. Raymond via devel
  • Re: What's left to doo on NTS Gary E. Miller via devel
  • Re: What's left to doo on NTS Eric S. Raymond via devel
  • Re: What's left to doo on NTS Gary E. Miller via devel
  • Re: What's left to doo on NTS Gary E. Miller via devel
  • Re: What's left to doo on NTS Hal Murray via devel
  • Re: What's left to doo on NTS Gary E. Miller via devel
  • Re: What's left to doo on NTS Matthew Selsky via devel
  • Re: What's left to doo on NTS Gary E. Miller via devel
  • Re: What's left to doo on NTS Hal Murray via devel
  • Re: What's left to doo on NTS Eric S. Raymond via devel
  • Re: What's left to doo on NTS Hal Murray via devel
  • Re: What's left to doo on NTS Gary E. Miller via devel
  • Re: What's left to doo on NTS Hal Murray via devel
  • Re: What's left to doo on NTS Gary E. Miller via devel
  • Re: What's left to doo on NTS Achim Gratz via devel

• Later messages