On Thu, 21 Jun 2007, Brian Ginsbach wrote:
> I'd like to make the following change to getopt_long(3).  The
> current NetBSD version of getopt_long(3) does not match the behavior
> of GNU getopt_long(3) when dealing with potentially abmiguous
> arguments.

Could you explain this in a way that doesn't require the reader to
reverse engineer the patch?  What is a "potentially ambiguous argument",
and what are the two behaviours?

--apb (Alan Barrett)