Taylor R Campbell writes:
> Well, what happened is:
>
> 1. I was drafting posix_memalign and aligned_alloc for libbsdmalloc in
>response to the thread about static program size yesterday, and
>carefully reading the specs -- POSIX 2018, C11 -- to make sure I
>got all the details right.
> Date: Wed, 05 Jul 2023 07:03:09 -0400
> From: Greg Troxel
> References: <20230705105858.33080f...@cvs.netbsd.org>
>
> "Taylor R Campbell" writes:
>
> > Revert "newfs(8): Ensure A divides S before aligned_alloc(A, S)."
> >
> > C17 lifted this restriction.
>
> I know we have only two toolchain
Date:Tue, 13 Sep 2016 00:50:30 +0100
From:Sevan Janiyan
Message-ID: <2d30ad57-2341-3b08-1d78-32b468cd5...@netbsd.org>
| I can't seem to find the 4.3BSD-Reno release notes at the moment, but
| the convention is interim releases do not count.
| There are examples
On 13/09/2016 00:09, matthew green wrote:
> that never stopped them being referenced before. infact, the macros
> appear know what they mean because it transforms:
>
>.Bx 4.3 tahoe .
>
> into:
>
>The shells file format appeared in 4.3BSD-Tahoe.
>
> ie, it capitalises and adds the dash.
Sevan Janiyan writes:
> On 12/09/2016 22:02, matthew green wrote:
> > wouldn't "09/06/89" put it in 4.3RENO ? from bsd-family-tree:
> >
> > 4.3BSD Reno 1990-06-29 [QCU], [DOC]
> >
> >
> > .mrg.
>
> Reno & Tahoe along with 4.1{a,b,c} were interim/beta releases.
that never stopped t
On 12/09/2016 22:02, matthew green wrote:
> wouldn't "09/06/89" put it in 4.3RENO ? from bsd-family-tree:
>
> 4.3BSD Reno 1990-06-29 [QCU], [DOC]
>
>
> .mrg.
Reno & Tahoe along with 4.1{a,b,c} were interim/beta releases.
> Log Message:
> Memory File System support appeared in 4.4BSD, implemented as an extension to
> newfs(8). So while newfs may have appeared in 4.2BSD, MFS support was later.
> https://svnweb.freebsd.org/csrg/sbin/newfs/Makefile?r1=39047&r2=39051
> Adjust HISTORY.
> Bump date.
wouldn't "09/06/89" p
