NetBSD Problem Report #21970

Received: (qmail 12807 invoked by uid 605); 23 Jun 2003 16:10:39 -0000
Message-Id: <200306231610.h5NGA8lK010536@apb.cequrux.com>
Date: Mon, 23 Jun 2003 18:10:08 +0200 (SAST)
From: Alan Barrett <apb@cequrux.com>
Sender: gnats-bugs-owner@netbsd.org
Reply-To: apb@cequrux.com
To: gnats-bugs@gnats.netbsd.org
Subject: printf(1) breaks when format begins with "-"
X-Send-Pr-Version: 3.95

>Number:         21970
>Category:       bin
>Synopsis:       printf(1) breaks when format begins with "-"
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    apb
>State:          closed
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jun 23 16:11:00 +0000 2003
>Closed-Date:    Mon Mar 12 00:46:04 +0000 2018
>Last-Modified:  Mon Mar 12 00:46:04 +0000 2018
>Originator:     Alan Barrett
>Release:        NetBSD 1.6T
>Organization:
not much
>Environment:
System: NetBSD 1.6T
Architecture: i386
Machine: i386
>Description:
	printf(1) is documented as not taking any options.  The
	first arg is supposed to be a format string.

	However, if the format string begins with "-" then printf(1)
	incorrectly treats it like an option.

>How-To-Repeat:
1. The following command should output "-foo<newline>".
   Instead, it produces an error.

    $ printf "-%s\n" "foo"
    sh: unknown option -- f
    usage: printf format [arg ...]

2. The following command should output "--foo<newline>".
   Instead, it produces an error.

    $ printf "--%s\n" "foo"
    sh: unknown option -- -
    usage: printf format [arg ...]

3. The following command should output "-" (without a newline),
   and it works correctly.

    $ printf "-"
    -$

4. The following command should output "--" (without a newline).
   Instead, it produces an error.

    $ printf "--"
    printf: usage: printf format [arguments]

5. The following command should treat the first arg as a format string;
   so it should output "--" (without a newline), and it should ignore
   the second and third args.  Instead, it ignores the first arg, treats
   the second arg as a format string, and interpolates the third arg as
   a parameter in the format string.

    $ printf -- "--%s\n" "foo"
    --foo

>Fix:
To make the behaviour match the documentation, remove the getopt() loop
at the top of src/bin/printf/printf.c

Alternatively, if the observed behaviour is actually the desired
behaviour, then fix the documentation to: (1) mention the special
treatment of "--"; (2) mention that the format string may not begin with
"-", unless it is preceded by a special "--" arg.

>Release-Note:
>Audit-Trail:

From: Ben Harris <bjh21@netbsd.org>
To: gnats-bugs@gnats.netbsd.org
Cc:  
Subject: bin/21970: printf(1) breaks when format begins with "-"
Date: Mon, 23 Jun 2003 17:23:22 +0100 (BST)

 Be careful.  POSIX lists printf's options as "None", which means that
 implementations are allowed to add options, so portable applications are
 required to use "--" before a first operand that begins with '-'.

 As such, examples 1, 2, and 3 are undefined by POSIX (so what we do is up
 to us), I'm not entirely sure about 4, and 5 is defined by POSIX to behave
 as NetBSD's implementation currently does.

 I'd recommend fixing the documentation, though this actually needs doing
 for pretty much every command that uses getopt().  Alternatively, perhaps
 we should put it in intro(1).

 -- 
 Ben Harris                                                   <bjh21@netbsd.org>
 Portmaster, NetBSD/acorn26           <URL:http://www.netbsd.org/Ports/acorn26/>


From: David Laight <dsl@netbsd.org>
To: gnats-bugs@gnats.netbsd.org
Cc:  
Subject: pr/21970 CVS commit: src/usr.bin/printf
Date: Wed, 25 Jun 2003 09:54:16 +0000 (UTC)

 Module Name:	src
 Committed By:	dsl
 Date:		Wed Jun 25 09:54:16 UTC 2003

 Modified Files:
 	src/usr.bin/printf: printf.c

 Log Message:
 Remove getopt() loop, IEEE 1003.1 doesn't say that printf(1) should conform
 to the "Utility Syntax Guidlines".
 Fixes PR 21970.


 To generate a diff of this commit:
 cvs rdiff -r1.26 -r1.27 src/usr.bin/printf/printf.c

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

State-Changed-From-To: open->closed 
State-Changed-By: dsl 
State-Changed-When: Wed Jun 25 09:55:12 UTC 2003 
State-Changed-Why:  
I've removed the getopt() loop. 
IEEE 1003.1 doesn't say that printf(1) should conform to the "Utility 
Syntax Guidlines". 

From: David Laight <david@l8s.co.uk>
To: Alan Barrett <apb@cequrux.com>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: bin/21970: printf(1) breaks when format begins with "-"
Date: Wed, 25 Jun 2003 14:14:08 +0100

 > >Synopsis:       printf(1) breaks when format begins with "-"

 > 	printf(1) is documented as not taking any options.  The
 > 	first arg is supposed to be a format string.
 > 
 > 	However, if the format string begins with "-" then printf(1)
 > 	incorrectly treats it like an option.

 This is the correct behaviour.  IEEE 1003.1 requires that implemenations
 are allowed to add options, so the standard option parsing rules apply.

 The printf(1) code has been reverted to its former state.

 	David

 -- 
 David Laight: david@l8s.co.uk

From: Alan Barrett <apb@cequrux.com>
To: David Laight <david@l8s.co.uk>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: bin/21970: printf(1) breaks when format begins with "-"
Date: Wed, 25 Jun 2003 16:00:51 +0200

 On Wed, 25 Jun 2003, David Laight wrote:
 > > >Synopsis:       printf(1) breaks when format begins with "-"
 > 
 > This is the correct behaviour.  IEEE 1003.1 requires that implemenations
 > are allowed to add options, so the standard option parsing rules apply.

 In that case, the documentation should be fixed.  The following patch
 to the printf(1) man page might help, but a complete fix should involve
 nearly all man pages in section 1.

 --- printf.1	28 Apr 2003 09:38:19 -0000	1.19
 +++ printf.1	25 Jun 2003 13:52:10 -0000
 @@ -36,7 +36,7 @@
  .\"
  .\"	from: @(#)printf.1	8.1 (Berkeley) 6/6/93
  .\"
 -.Dd November 5, 1993
 +.Dd June 25, 2003
  .Dt PRINTF 1
  .Os
  .Sh NAME
 @@ -44,6 +44,7 @@
  .Nd formatted output
  .Sh SYNOPSIS
  .Nm
 +.Op Fl -
  .Ar format
  .Op Ar arguments  ...
  .Sh DESCRIPTION
 @@ -59,9 +60,21 @@
  each of which causes printing of the next successive
  .Ar argument  .
  .Pp
 -The
 +The optional
 +.Fl -
 +argument may be used to ensure that the
 +.Ar format
 +argument is interpreted correctly, even if the
 +.Ar format
 +begins with a
 +.Dq -
 +character.
 +.Pp
 +The remaining
  .Ar arguments
 -after the first are treated as strings if the corresponding format is
 +(if any) after the
 +.Ar format
 +are treated as strings if the corresponding format is
  either
  .Cm b ,
  .Cm B ,
 @@ -375,6 +388,11 @@
  .Nm
  utility conforms to
  .St -p1003.1-2001 .
 +As a consequence of this,
 +.Nm
 +recognises
 +.Dq Fl -
 +as a first argument to be discarded.
  .Pp
  Support for the floating point formats and `*' as a field width and precision
  are optional in POSIX.

From: Alan Barrett <apb@cequrux.com>
To: David Laight <david@l8s.co.uk>
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: bin/21970: printf(1) breaks when format begins with "-"
Date: Thu, 26 Jun 2003 14:38:29 +0200

 On Wed, 25 Jun 2003, David Laight wrote:
 > > >Synopsis:       printf(1) breaks when format begins with "-"
 > The printf(1) code has been reverted to its former state.

 Please re-open the PR.  It should not be closed before the
 documentation is fixed.

 --apb (Alan Barrett)

From: David Laight <david@l8s.co.uk>
To: netbsd-bugs@netbsd.org
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: bin/21970: printf(1) breaks when format begins with "-"
Date: Thu, 26 Jun 2003 16:49:08 +0100

 > In that case, the documentation should be fixed.  The following patch
 > to the printf(1) man page might help, but a complete fix should involve
 > nearly all man pages in section 1.

 I disagree, repeating that information in all the man pages is pointless
 and error prone.

 intro(1) should probably describe some of what is in:

 http://www.opengroup.org/onlinepubs/007904975/basedefs/xbd_chap12.html

 	David

 -- 
 David Laight: david@l8s.co.uk

From: Alan Barrett <apb@cequrux.com>
To: David Laight <david@l8s.co.uk>
Cc: netbsd-bugs@netbsd.org, gnats-bugs@gnats.netbsd.org
Subject: Re: bin/21970: printf(1) breaks when format begins with "-"
Date: Thu, 26 Jun 2003 18:36:40 +0200

 On Thu, 26 Jun 2003, David Laight wrote:
 > > In that case, the documentation should be fixed.  The following patch
 > > to the printf(1) man page might help, but a complete fix should involve
 > > nearly all man pages in section 1.
 > 
 > I disagree, repeating that information in all the man pages is pointless
 > and error prone.

 Note that I have NOT suggested adding lots of information to all the
 man pages.  If that's the idea that you disagree with, then I also
 disagree with it.

 I have suggested adding a little bit of information to almost all the
 section 1 man pages: specifically, adding "[--]" to the synopsis of all
 relevant man pages.  This should be in conjunction with adding much more
 information to intro(1).

 When I sent that patch to printf(1), I should have emphasised that such
 a patch is my second last choice: better than doing nothing, but much
 worse than fixing intro(1) properly and adding "[--]" to almost all
 relevant synopsis sections.

 > intro(1) should probably describe some of what is in:
 > 
 > http://www.opengroup.org/onlinepubs/007904975/basedefs/xbd_chap12.html

 Yes, I agree.

 --apb (Alan Barrett)
State-Changed-From-To: closed->open 
State-Changed-By: dsl 
State-Changed-When: Thu Jun 26 17:08:13 UTC 2003 
State-Changed-Why:  
intro(1) man page needsexplanation of command line syntax 
Responsible-Changed-From-To: bin-bug-people->hubertf
Responsible-Changed-By: hubertf@netbsd.org
Responsible-Changed-When: Mon, 27 Nov 2006 00:42:17 +0000
Responsible-Changed-Why:
let's try


State-Changed-From-To: open->feedback
State-Changed-By: hubertf@netbsd.org
State-Changed-When: Mon, 27 Nov 2006 00:42:17 +0000
State-Changed-Why:
I've sent out a patch as a suggestion, but I'm not sure this came through
properly, so here it is again... if I missed the point, please let me
know or do the cut&paste yourself, see also localsrc/legal/TheOpenGroup
while there.


 - Hubert

P.S.: I also have a patch that has  12.1 Utility Argument Syntax
of the SUSv3 in *roff format, just in case that's what you want to have
in that manpage. Let me know if so!


So, here's my proposed patch:

Index: intro.1
===================================================================
RCS file: /cvsroot/src/share/man/man1/intro.1,v
retrieving revision 1.10
diff -u -r1.10 intro.1
--- intro.1     10 Nov 2004 16:35:57 -0000      1.10
+++ intro.1     27 Nov 2006 00:30:08 -0000
@@ -29,7 +29,7 @@
 .\"
 .\"     @(#)intro.1    8.2 (Berkeley) 12/30/93
 .\"
-.Dd April 21, 1998
+.Dd November 27, 2006
 .Dt INTRO 1
 .Os
 .Sh NAME
@@ -50,6 +50,18 @@
 formatted output tools,
 and line printer commands.
 .Pp
+Many of the commands use the
+.Xr getopt 3
+function for parsing of command line options.
+For those commands the argument
+.Dq --
+is accepted as a delimiter to indicate the end of options.
+Any following arguments are treated as operands, even if they begin with the
+.Sq -
+character. The
+.Dq --
+argument are not used as an option or as an operand.
+.Pp
 All commands set a status value upon exit which may be tested
 to see if the command completed normally.
 The exit values and their meanings are explained in the individual


From: Hubert Feyrer <hubert@feyrer.de>
To: apb@NetBSD.org, dsl@NetBSD.org
Cc: gnats-bugs@NetBSD.org
Subject: Re: bin/21970 - printf(1) breaks when format begins with "-"
Date: Mon, 27 Nov 2006 01:36:40 +0100 (CET)

 Hi,

 I'm not sure what part exactly you think should be added to intro.1, but 
 below is an educated guess. If I took the wrong one let me know (or do the 
 cut&paste yourself - see also localsrc/legal/TheOpenGroup!).


   - Hubert


 Index: intro.1
 ===================================================================
 RCS file: /cvsroot/src/share/man/man1/intro.1,v
 retrieving revision 1.10
 diff -u -r1.10 intro.1
 --- intro.1	10 Nov 2004 16:35:57 -0000	1.10
 +++ intro.1	27 Nov 2006 00:30:08 -0000
 @@ -29,7 +29,7 @@
   .\"
   .\"     @(#)intro.1	8.2 (Berkeley) 12/30/93
   .\"
 -.Dd April 21, 1998
 +.Dd November 27, 2006
   .Dt INTRO 1
   .Os
   .Sh NAME
 @@ -50,6 +50,18 @@
   formatted output tools,
   and line printer commands.
   .Pp
 +Many of the commands use the
 +.Xr getopt 3
 +function for parsing of command line options.
 +For those commands the argument
 +.Dq --
 +is accepted as a delimiter to indicate the end of options.
 +Any following arguments are treated as operands, even if they begin with the
 +.Sq -
 +character. The
 +.Dq --
 +argument are not used as an option or as an operand.
 +.Pp
   All commands set a status value upon exit which may be tested
   to see if the command completed normally.
   The exit values and their meanings are explained in the individual

From: Hubert Feyrer <hubert@feyrer.de>
To: gnats-bugs@NetBSD.org, apb@NetBSD.org, dsl@NetBSD.org
Cc: netbsd-bugs@netbsd.org
Subject: Re: bin/21970 - printf(1) breaks when format begins with "-"
Date: Mon, 27 Nov 2006 01:55:46 +0100 (CET)

 FWIW here's a better patch that doesn't use TOG wording:

 Index: intro.1
 ===================================================================
 RCS file: /cvsroot/src/share/man/man1/intro.1,v
 retrieving revision 1.10
 diff -u -r1.10 intro.1
 --- intro.1	10 Nov 2004 16:35:57 -0000	1.10
 +++ intro.1	27 Nov 2006 00:56:18 -0000
 @@ -50,6 +202,16 @@
   formatted output tools,
   and line printer commands.
   .Pp
 +Many of the commands use the
 +.Xr getopt 3
 +function for parsing of command line options.
 +For those commands the argument
 +.Dq --
 +indicates the end of options, and any following arguments
 +are assumed to be operands, even if they begin with a
 +.Sq -
 +character.
 +.Pp
   All commands set a status value upon exit which may be tested
   to see if the command completed normally.
   The exit values and their meanings are explained in the individual


   - Hubert

From: Alan Barrett <apb@cequrux.com>
To: gnats-bugs@NetBSD.org
Cc: netbsd-bugs@NetBSD.org
Subject: Re: bin/21970 (printf(1) breaks when format begins with "-")
Date: Mon, 27 Nov 2006 09:21:24 +0400

 On Mon, 27 Nov 2006, hubertf@NetBSD.org wrote:
 > I've sent out a patch as a suggestion, but I'm not sure this came through
 > properly, so here it is again... if I missed the point, please let me
 > know or do the cut&paste yourself, see also localsrc/legal/TheOpenGroup
 > while there.
 > 
 > 
 >  - Hubert
 > 
 > P.S.: I also have a patch that has  12.1 Utility Argument Syntax
 > of the SUSv3 in *roff format, just in case that's what you want to have
 > in that manpage. Let me know if so!

 Thanks Hubert.  I think it would be useful to add something to
 intro(1) explaining that most utilities accept "--" for "end
 of options", "-xyz" often means the same as "-x" "-y" "-z",
 "-oarg" often means the same as "-o" "arg", option order usually
 doesn't matter, etc.  I'd prefer a level of detail somewhere
 between your proposed patch and the text from SUSv3 section 12.1
 <http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap12.html>,
 but your patch is good enough.

 I still think it's a bug that printf(1) uses getopt.  I think it's wrong for
 any utility that doesn't take options in the usual way to use getopt().

 If you compare the SUSv3 descriptions of printf(1) and cat(1)
 (<http://www.opengroup.org/onlinepubs/009695399/utilities/printf.html>
 and <http://www.opengroup.org/onlinepubs/009695399/utilities/cat.html>),
 you can see that "The cat utility shall conform to the Base Definitions
 volume of IEEE Std 1003.1-2001, Section 12.2, Utility Syntax
 Guidelines", whereas printf(1) does not.

 I don't buy the argument that "OPTIONS None" in SUSv3 means "anybody who
 uses printf(1) needs to insert "--" to guarantee that the format is not
 misinterpreted as an option".  At least, not unless somebody can point
 to text in SUSv3 that says so.

 --apb (Alan Barrett)

From: David Laight <david@l8s.co.uk>
To: 
Cc: gnats-bugs@NetBSD.org
Subject: Re: bin/21970 (printf(1) breaks when format begins with "-")
Date: Mon, 27 Nov 2006 21:45:58 +0000

 On Mon, Nov 27, 2006 at 09:21:24AM +0400, Alan Barrett wrote:
 > 
 > I still think it's a bug that printf(1) uses getopt.  I think it's wrong for
 > any utility that doesn't take options in the usual way to use getopt().

 From:
 http://www.opengroup.org/onlinepubs/009695399/xrat/xbd_chap12.html

 Applications calling any utility with a first operand starting with '-'
 should usually specify --, as indicated by Guideline 10, to mark the end of
 the options.  This is true even if the SYNOPSIS in the Shell and Utilities
 volume of IEEE Std 1003.1-2001 does not specify any options; implementations
 may provide options as extensions to the Shell and Utilities volume of IEEE
 Std 1003.1-2001.  The standard utilities that do not support Guideline 10
 indicate that fact in the OPTIONS section of the utility description.

 	David

 -- 
 David Laight: david@l8s.co.uk

From: Hubert Feyrer <hubert@feyrer.de>
To: gnats-bugs@NetBSD.org, dsl@NetBSD.org, apb@NetBSD.org
Cc: gnats-admin@netbsd.org, netbsd-bugs@netbsd.org, apb@cequrux.com
Subject: Re: bin/21970 (printf(1) breaks when format begins with "-")
Date: Tue, 28 Nov 2006 00:42:18 +0100 (CET)

 On Mon, 27 Nov 2006, David Laight wrote:
 > From:
 > http://www.opengroup.org/onlinepubs/009695399/xrat/xbd_chap12.html
 >
 > Applications calling any utility with a first operand starting with '-'
 > should usually specify --, as indicated by Guideline 10, to mark the end of
 > the options.  This is true even if the SYNOPSIS in the Shell and Utilities
 > volume of IEEE Std 1003.1-2001 does not specify any options; implementations
 > may provide options as extensions to the Shell and Utilities volume of IEEE
 > Std 1003.1-2001.  The standard utilities that do not support Guideline 10
 > indicate that fact in the OPTIONS section of the utility description.

 So now that we know that NetBSD's printf(1) conforms to SUSv3, what do we 
 do? I'm inclined to close the PR, and let you two (apb, dsl) think about 
 documentation.

 Any objections?


   - Hubert

From: Alan Barrett <apb@netbsd.org>
To: Hubert Feyrer <hubert@feyrer.de>
Cc: gnats-bugs@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: bin/21970 (printf(1) breaks when format begins with "-")
Date: Tue, 28 Nov 2006 22:38:26 +0400

 On Tue, 28 Nov 2006, Hubert Feyrer wrote:
 > So now that we know that NetBSD's printf(1) conforms to SUSv3, what do we 
 > do? I'm inclined to close the PR, and let you two (apb, dsl) think about 
 > documentation.
 > 
 > Any objections?

 Please leave it open; assign it to me if you like, but I won't be
 writing documentation (or even reading fine print in SUSv3) before
 January.

 --apb (Alan Barrett)

Responsible-Changed-From-To: hubertf->apb
Responsible-Changed-By: hubertf@netbsd.org
Responsible-Changed-When: Tue, 28 Nov 2006 23:10:55 +0000
Responsible-Changed-Why:
apb wants to keep this open


State-Changed-From-To: feedback->analyzed
State-Changed-By: hubertf@netbsd.org
State-Changed-When: Tue, 28 Nov 2006 23:10:55 +0000
State-Changed-Why:
We've found that printf(1)'s behaviour conforms to SUSv3.
apb@ wants it still open, so he can work on documentation starting 
Jan 2007 ...


 - Hubert


From: Alan Barrett <apb@cequrux.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: bin/21970 (printf(1) breaks when format begins with "-")
Date: Tue, 4 Nov 2008 09:26:56 +0200

 On Mon, 27 Nov 2006, Alan Barrett wrote:
 > I don't buy the argument that "OPTIONS None" in SUSv3 means "anybody who
 > uses printf(1) needs to insert "--" to guarantee that the format is not
 > misinterpreted as an option".  At least, not unless somebody can point
 > to text in SUSv3 that says so.

 I have now found text in SUSv3 that supports the argument that I
 rejected before.

 Under "Utility Description Defaults" at
 <http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap01.html
 #tag_01_11>, under the "OPTIONS" subheading, it says

 "       When this section is listed as "None.", it means that the
 "       implementation need not support any options. Standard utilities
 "       that do not accept options, but that do accept operands, shall
 "       recognize "--" as a first argument to be discarded.

 I am now convinced that NetBSD's printf(1) utility's handling of the
 "--" option is correct per SUSv3.  Treating a format argument that
 just happens to begin with "-" as if it was an unrecognised option is
 probably also allowed as an implementation extension, though I haven't
 found specific text to support that theory.

 The only remaining problem is that this use of "--" is poorly
 documented.  I will work on that when I have time.

 --apb (Alan Barrett)

From: David Laight <david@l8s.co.uk>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: bin/21970 (printf(1) breaks when format begins with "-")
Date: Tue, 4 Nov 2008 18:19:06 +0000

 On Tue, Nov 04, 2008 at 07:30:05AM +0000, Alan Barrett wrote:
 >  
 >  I have now found text in SUSv3 that supports the argument that I
 >  rejected before.
 >  
 >  Under "Utility Description Defaults" at
 >  <http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap01.html
 >  #tag_01_11>, under the "OPTIONS" subheading, it says
 >  
 >  "       When this section is listed as "None.", it means that the
 >  "       implementation need not support any options. Standard utilities
 >  "       that do not accept options, but that do accept operands, shall
 >  "       recognize "--" as a first argument to be discarded.
 >  
 >  I am now convinced that NetBSD's printf(1) utility's handling of the
 >  "--" option is correct per SUSv3.  Treating a format argument that
 >  just happens to begin with "-" as if it was an unrecognised option is
 >  probably also allowed as an implementation extension, though I haven't
 >  found specific text to support that theory.

 My intepretation of the SUSv3 text is that the behaviour of NetBSD's
 printf(1) is required ...

 The real point is that "None." means that no options are currently
 supported, but some may be added in a future vresion.

 	David

 -- 
 David Laight: david@l8s.co.uk

From: "David A. Holland" <dholland@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc: 
Subject: PR/21970 CVS commit: src/usr.bin/printf
Date: Mon, 12 Mar 2018 00:42:06 +0000

 Module Name:	src
 Committed By:	dholland
 Date:		Mon Mar 12 00:42:06 UTC 2018

 Modified Files:
 	src/usr.bin/printf: printf.1

 Log Message:
 Explicitly mention use of -- for format strings beginning with -,
 per PR 21970.


 To generate a diff of this commit:
 cvs rdiff -u -r1.25 -r1.26 src/usr.bin/printf/printf.1

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

State-Changed-From-To: analyzed->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Mon, 12 Mar 2018 00:46:04 +0000
State-Changed-Why:
I fixed the docs, the rest was sorted out ages ago.


>Unformatted:

Home	PR Database Search