Re: CVS commit: src/usr.bin/printf

2020-06-29 Thread Robert Elz
Date:Sun, 28 Jun 2020 22:58:52 +0300 From:Valery Ushakov Message-ID: <20200628195852.gc20...@pony.stderr.spb.ru> | but I'd expect people that actually use IFS with octal digits | or a backslash to also understand and know how to add necessary | quoting in that

Re: CVS commit: src/usr.bin/printf

2020-06-28 Thread Valery Ushakov
On Sun, Jun 28, 2020 at 21:52:23 +0700, Robert Elz wrote: > Date:Fri, 26 Jun 2020 22:05:05 + > From:"Valeriy E. Ushakov" > Message-ID: <20200626220505.e9030f...@cvs.netbsd.org> > > | Modified Files: > | src/usr.bin/printf: printf.1 > | > | Log Message:

Re: CVS commit: src/usr.bin/printf

2020-06-28 Thread Robert Elz
Date:Fri, 26 Jun 2020 22:05:05 + From:"Valeriy E. Ushakov" Message-ID: <20200626220505.e9030f...@cvs.netbsd.org> | Modified Files: | src/usr.bin/printf: printf.1 | | Log Message: | Drop redundant quoting in the nested printf example. I don't think

Re: CVS commit: src/usr.bin/printf

2019-07-22 Thread Tobias Nygren
On Tue, 23 Jul 2019 00:31:32 +0700 Robert Elz wrote: > Date:Mon, 22 Jul 2019 12:23:35 +0200 > From:Tobias Nygren > Message-ID: <20190722122335.55c0d421a18a082c8d67b...@netbsd.org> > > | Please exercise caution when changing established userland behaviour. > |

Re: CVS commit: src/usr.bin/printf

2019-07-22 Thread Robert Elz
Date:Mon, 22 Jul 2019 12:23:35 +0200 From:Tobias Nygren Message-ID: <20190722122335.55c0d421a18a082c8d67b...@netbsd.org> | Please exercise caution when changing established userland behaviour. | This change broke the pkgsrc/lang/openjdk8(1) build. I stand behind

Re: CVS commit: src/usr.bin/printf

2019-07-22 Thread Robert Elz
Date:Mon, 22 Jul 2019 12:23:35 +0200 From:Tobias Nygren Message-ID: <20190722122335.55c0d421a18a082c8d67b...@netbsd.org> | This change broke the pkgsrc/lang/openjdk8(1) build. That it is broken and ought to be patched upstream, it is quite clear that printf is

Re: CVS commit: src/usr.bin/printf

2019-07-22 Thread Tobias Nygren
On Sun, 21 Jul 2019 15:25:39 + Robert Elz wrote: > Module Name: src > Committed By: kre > Date: Sun Jul 21 15:25:39 UTC 2019 > > Modified Files: > src/usr.bin/printf: printf.c > > Log Message: > Stop assuming that printf handles options in any way at all > (it doesn't - that

Re: CVS commit: src/usr.bin/printf

2019-01-27 Thread Robert Elz
Actually, I suspect now that what I remember reading was the rationale in the page in XCU section 4 for the printf command. kre

Re: CVS commit: src/usr.bin/printf

2019-01-27 Thread Robert Elz
Date:Sun, 27 Jan 2019 18:42:22 +0300 From:Valery Ushakov Message-ID: <20190127154222.gg18...@pony.stderr.spb.ru> | This was changed in Issue 7. The link to the Austin group | interpretations repository seems to be broken, though. Where can I | find the text

Re: CVS commit: src/usr.bin/printf

2019-01-27 Thread Valery Ushakov
On Sun, Jan 27, 2019 at 12:03:09 +, Robert Elz wrote: > Modified Files: > src/usr.bin/printf: printf.c > > Log Message: > Revert previous, it was based upon a misreading of the POSIX > spec. POSIX requires "as if by calling strtod()" which we > did already ... by calling strtod().