Emacs master reset over LLM commit

Emacs developers force-reset the master branch to excise an LLM-coauthored commit that breached GNU interim policy, with follow-on discussion of local clone recovery and prevention measures. Separate threads covered a Blender node proposal, a Rust kernel IO refactor, and a heated KDE session-manager demand.

Emacs master branch force-reset

The emacs.git master branch was force-reset to drop a commit carrying LLM authorship issues. Participants on emacs-devel discussed recovery steps for developers with local clones that had already pulled the discarded history. Readers tracking Emacs should note the rewrite because it affects ongoing work and clone hygiene.

Debate over LLM-coauthored Emacs commit

An accidental LLM-coauthored commit landed in upstream master, prompting a heated emacs-devel thread against the GNU interim policy on such contributions. Contributors proposed pre-commit hooks and weighed a possible history rewrite to keep the tree clean. The exchange matters for anyone submitting to GNU projects, as it clarifies enforcement expectations around generated code.

Penny Noise variants proposed for Blender

A developer floated Penny Noise node variants on the Blender DevTalk forum. Core developers examined integration points, existing node architecture constraints, and the role of AI-assisted code in the implementation. Node authors and shader writers will care because the outcome shapes how new procedural textures enter the tree.

Typed register bases in Rust kernel IO

A ten-patch series on dri-devel refactors Rust kernel IO register macros so that bases must be typed and relative registers give way to subregion projection. The change tightens compile-time safety for drivers that map hardware registers. Kernel and DRM Rust contributors should review it for impact on existing register-access patterns.

ksmserver Wayland rewrite demand

A user on the KDE Discuss forum demanded that ksmserver be rewritten for pure Wayland compatibility. Other participants cited community guidelines on tone, after which the original poster apologized. The exchange is a minor reminder of how session-management work is prioritized inside Plasma.