Emacs 31.1, LLM packaging debate, Blender nodes

Emacs development produced both a numbered release and a heated governance exchange over LLM-assisted packages, while Blender and DRM lists advanced node and driver proposals. The day mixed release logistics with design feedback on lighting nodes, geometry assets, and Rust ID handling for graphics drivers.

Magit-inspired Sapling client and LLM code policy

An ELPA submission for an LLM-assisted Sapling client modeled on Magit prompted extended discussion on emacs-devel. Richard Stallman joined the debate over whether to reject LLM-generated code and what headers would be suitable, across 43 messages from six participants. The exchange matters for anyone tracking Emacs package acceptance rules and AI contribution norms.

Emacs 31.1 source and binaries announced

Emacs 31.1 source tarballs and Windows binaries were posted to emacs-devel. The ensuing thread of 31 messages from 14 participants included a minor build bug report plus clarifications on terminology for adding packages. Users and packagers gain a concrete new baseline to test and ship against.

Material Lighting Nodes feedback for Blender 5.3

An experimental Material Lighting Nodes proposal covering Light Info and Shadow Raycast drew active technical feedback on the Blender developers forum. Twenty-four participants posted 77 messages aimed at a Blender 5.3 target. Node authors and look-development artists have a live channel to shape the lighting data model before it freezes.

Rust ID range reservation for DRM

Version 8 of a patch series on dri-devel adds Rust bindings for bitmap range reservation together with an IdPool used by nova-core channel ID allocation. Seven participants exchanged 33 messages refining the approach. Kernel graphics developers working in Rust gain a clearer path for safe ID pool management.

Geometry Nodes Curve to Tube asset controls

Users asked for integrated trim controls on the Curve to Tube geometry nodes asset planned for Blender 5.0. Core developers replied in favor of keeping separate modular modifiers instead, across 13 messages from six people. The discussion clarifies the maintainers preference for composable assets over convenience wrappers.

StarFive JH7110 display subsystem enablement

A second revision of a 15-patch series enables the StarFive JH7110 display and HDMI path on dri-devel by splitting a monolithic IP block to fix clock dependencies. AI-assisted reviews flagged several bugs during the 38-message thread involving six participants. Embedded graphics work on this platform moves forward with the cleaned-up series.