On Fri, Nov 04, 2016 at 03:31:18PM +0100, Miroslav Lichvar wrote: > Ok, so the option should be called print-tag, log-tag, message-tag, or > something else?
'message_tag' seems best to me. > I wouldn't mind if phc2sys and pmc supported config files, but I think > this particular option might be one of those that make more sense to > be used on command line rather than config file. If I wanted to run > multiple ptp4l instances with different tags for their log messages, > I could still share the config file between them if I specified the > interface and tag on the command line. Ok, that is a reason. But please can we have '-t' instead of '-o'? -o makes me think of "output file". > Would it be less confusing if we introduced GNU-style long option > names? Not to me. PTP has tons of options, and every new profile forces more and more of these. I simply find it gross when programs have a gazillion command line options. It makes for poor usability. I really wanted ptp4l to have the "top ten" options available on the command line, in order to keep it simple for the most common use cases. I think we should consider the long options for v2 if people really want them... Thanks, Richard ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
