On Mon, Jul 19, 2021 at 11:00:40AM +, Geva, Erez wrote:
> This looks like a call to send the a patch with these options.
>
> Richard, How do you think these options should be implemented?
> A single enumerator, separate integer for each?
Whichever is easier. Maybe a single code like 8n1 pars
In the groff syntax lines starting with a dot or quote are requests. A
line in the servo_offset_threshold description starts with a quote,
which breaks the output. Move a word to the beginning of the line to fix
it.
Signed-off-by: Miroslav Lichvar
---
ptp4l.8 | 4 ++--
1 file changed, 2 insertio
Hi,
Do you mean this one, page 20?
http://www.leapsecond.com/museum/z3801a/097-z3801-01-iss-1.pdf
Erez
-Original Message-
From: Richard Cochran
Sent: Monday, 19 July 2021 04:13
To: Hal Murray
Cc: linuxptp-devel@lists.sourceforge.net
Subject: Re: [Linuxptp-devel] [PATCH 4/4] ts2phc: Ad
This looks like a call to send the a patch with these options.
Richard, How do you think these options should be implemented?
A single enumerator, separate integer for each?
Erez
-Original Message-
From: Hal Murray
Sent: Monday, 19 July 2021 12:39
To: Geva, Erez (ext) (DI PA DCP R&D 3)
erez.geva@siemens.com said:
> Do you mean this one, page 20?
> http://www.leapsecond.com/museum/z3801a/097-z3801-01-iss-1.pdf
Yes, but look down on page 93 (or 5-3)
> Baud Rate: 19200--7 data bits, 1 start bit, 1 stop bit, odd parity
> (fixed configuration).
--
These are my opinions.
On Sun, Jul 18, 2021 at 07:46:50PM -0700, Richard Cochran wrote:
> On Tue, Jul 13, 2021 at 10:31:16AM +0200, Miroslav Lichvar wrote:
> > getopt_long() in glibc allows shortened long option names, e.g.
> > ptp4l --domain works as --domainNumber. When the match is ambiguous,
> > e.g. --fault matches