Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10]
- Reply: Bjoern A. Zeeb: "Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10]"
- Reply: Ed Maste : "Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10]"
- In reply to: Mark Millard : "RE: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10]"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 09 Nov 2025 07:00:20 UTC
On 11/8/25 20:26, Mark Millard wrote: > Steve Kargl <kargls_at_comcast.net> wrote on > Date: Sun, 09 Nov 2025 01:55:40 UTC : > >> Can someone back out the git commit 4179e6b78297369f? >> This is causing pkg-fallout@ to spam the freebsd-x11 >> mailing list. It seems no one reads replies to pkg-fallout. >> See for detail >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290432 > > > It appears that commit is in stable/15 and in releng/15.0 as: > > https://cgit.freebsd.org/src/commit/sys/compat/linuxkpi/common?h=releng/15.0&id=62c3b77d1d1084dc46663eed52e288307b5c7e64 > > Your request is probably a very big ask as this point. Yes, the patch was merged into stable/15. It should not have been! It's not a big ask. Either back out the commit or maybe, just maybe, someone can commit the patch in PR290432. There are dozens of pkg-fallout@ emails to freebsd-x11. Many have a reply from me pointing to the patch in PR290432. So, either back out the patch that breaks X11 for many people or commit the patch in the PR. -- steve