On Sun, Jun 25, 2023 at 07:07:33PM -0300, Lucas de Sena wrote:
> The manual already describes how posix_spawn(3) behaves when passing it
> a NULL envp, but does not make it clear that it is an OpenBSD extension:
>
> > If envp is NULL, the environment is passed unchanged from the parent
> > process
wrong mailing list, moved to ports@ & reply-to set.
On 2023/06/24 23:02, Alfred Morgan wrote:
> bzr got deleted from openbsd ports about 2 years ago (died along with
> Python2).
> https://cvsweb.openbsd.org/ports/devel/bzr/Attic/Makefile?only_with_tag=HEAD
> bzr was superseded by brz but brz never
Hello,
The new code looks much better. It's huge leap forward. I don't mind if this
big diff will get committed. Hrvoje did test the whole diff. Trying to split it
to smaller changes might bring in code which is not tested enough. We don't
know how individual pieces work independently.
I've got
Todd C. Miller wrote:
> Other implementations of "time -p" (both builtin and standalone)
> only display two digits after the radix point. I'm a little concerned
> about breaking scripts that consume out the output of "time -p".
I share that concern.
Other implementations of "time -p" (both builtin and standalone)
only display two digits after the radix point. I'm a little concerned
about breaking scripts that consume out the output of "time -p".
Changing the precission of the non-portable output format is fine.
- todd
The manual already describes how posix_spawn(3) behaves when passing it
a NULL envp, but does not make it clear that it is an OpenBSD extension:
> If envp is NULL, the environment is passed unchanged from the parent
> process.
That differs from GNU/Linux, for example, where a NULL envp gives the
On Tue, Jun 13, 2023 at 10:59:53PM -0500, Scott Cheloha wrote:
> This patch bumps the precision of durations printed by csh(1), ksh(1),
> and time(1) from centiseconds to milliseconds. The csh(1) and ksh(1)
> builtins "time" and "times" are affected.
>
> My thinking is:
>
> - All practical OpenB
