Date: Mon, 27 Apr 2026 18:21:10 -0700 From: Mark Millard <marklmi@yahoo.com> To: Graham Percival <gperciva@tarsnap.com>, Bugs Beastie <bugsbeastie@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD Git Weekly 2026-04-20 to 2026-04-26 Message-ID: <0c74e047-996c-4247-80f2-d87cc7acc7b3@yahoo.com> In-Reply-To: <ae_8onDaijGiFGQJ@beastie.local> References: <ae-ONCD3HfsRSLWU@beastie.local> <71625ec7-2ffb-4af2-a57e-b07debe2f8e5@gmail.com> <ae_8onDaijGiFGQJ@beastie.local>
index | next in thread | previous in thread | raw e-mail
On 4/27/26 17:17, Graham Percival wrote: > On 2026-04-27, Bugs Beastie wrote: >>> I'm happy to announce FreeBSD git weekly for > 2026-04-20 -- 2026-04-26: >>> https://freebsd-git-weekly.tarsnap.net/2026-04-20.html >> >>> No highlighted commits this week. >> >> >> LLVM 21 import on 25th of April? >> (Just a heads-up :) > > Oops, I thought that was a minor update. I'm guessing that 7351d001 is > the best commit to highlight? Arguably 8f95b8 could be highlighted > instead (or as well), since it modifies __FREEBSD_version. > > I've manually marked 8f95b8 as "highlighted" and regenerated the html. > > Thanks for the suggestion! > - Graham > > The commits between 8f95b8b19088 and the earlier 7351d001fc7f are likely mostly important implementations of FreeBSD'isms for the clang/clang++/libc++ behavior. The even more recent b6d823e39072 is a "Fix up builds on Linux hosts after llvm 21.1.8 merge" (same day) and may be the better way to avoid referencing something with a known incompleteness as of earlier commits. -- === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0c74e047-996c-4247-80f2-d87cc7acc7b3>