Re: Import seq(1) from FreeBSD

2022-02-21 Thread Greg Steuck
"Todd C. Miller" writes: > On Sun, 13 Feb 2022 12:07:31 -0800, Greg Steuck wrote: > >> I noticed that despite the OKs the code didn't submitted. Should we >> revive this diff now and continue in the tree? >> >> I have vested interest: I don't want to fix up lang/ghc test suite which >> is full

Re: Import seq(1) from FreeBSD

2022-02-21 Thread Todd C . Miller
On Sun, 13 Feb 2022 12:07:31 -0800, Greg Steuck wrote: > I noticed that despite the OKs the code didn't submitted. Should we > revive this diff now and continue in the tree? > > I have vested interest: I don't want to fix up lang/ghc test suite which > is full of seq(1). Here's an updated diff

Re: Import seq(1) from FreeBSD

2022-02-13 Thread Greg Steuck
Jonathan Gray writes: > On Sun, Feb 13, 2022 at 12:07:31PM -0800, Greg Steuck wrote: >> Ingo Schwarze writes: >> >> > Hi Todd, >> > >> > in view of your arguments and sthen@'s OK, i'm also OK with this >> > going in. I think a bit of code cleanup and copy editing in the >> > manual page may

Re: Import seq(1) from FreeBSD

2022-02-13 Thread Jonathan Gray
On Sun, Feb 13, 2022 at 12:07:31PM -0800, Greg Steuck wrote: > Ingo Schwarze writes: > > > Hi Todd, > > > > in view of your arguments and sthen@'s OK, i'm also OK with this > > going in. I think a bit of code cleanup and copy editing in the > > manual page may be useful afterwards, but that can

Re: Import seq(1) from FreeBSD

2022-02-13 Thread Greg Steuck
Ingo Schwarze writes: > Hi Todd, > > in view of your arguments and sthen@'s OK, i'm also OK with this > going in. I think a bit of code cleanup and copy editing in the > manual page may be useful afterwards, but that can be done in the > tree, no need for playing patch ping pong. I noticed

Re: Import seq(1) from FreeBSD

2020-11-17 Thread Ingo Schwarze
Hi Todd, in view of your arguments and sthen@'s OK, i'm also OK with this going in. I think a bit of code cleanup and copy editing in the manual page may be useful afterwards, but that can be done in the tree, no need for playing patch ping pong. See below for answers to the individual points.

Re: Import seq(1) from FreeBSD

2020-11-16 Thread Todd C . Miller
On Mon, 16 Nov 2020 16:14:31 +0100, Ingo Schwarze wrote: > are you really sure this is a good idea? The version you sent is > wildly incompatible with GNU sed. So we add a non-standard utility > that exhibits different behaviour on different systems even though > a standard utility already

Re: Import seq(1) from FreeBSD

2020-11-16 Thread Ingo Schwarze
Hi Todd, are you really sure this is a good idea? The version you sent is wildly incompatible with GNU sed. So we add a non-standard utility that exhibits different behaviour on different systems even though a standard utility already exists for the purpose? Is this needed for porting work?

Re: Import seq(1) from FreeBSD

2020-11-16 Thread Stuart Henderson
On 2020/11/16 05:49, Todd C. Miller wrote: > This is originally from NetBSD but FreeBSD appears to have some > additional fixes. > > I know we have jot(1) but seq(1) is considerably easier to use for > simple things and at this point, most other systems have it. OK with me. If this goes in then

Import seq(1) from FreeBSD

2020-11-16 Thread Todd C . Miller
This is originally from NetBSD but FreeBSD appears to have some additional fixes. I know we have jot(1) but seq(1) is considerably easier to use for simple things and at this point, most other systems have it. - todd Index: usr.bin/seq/Makefile