On Fri, Jun 05, 2026 at 02:48:14PM +0200, Stefan Eissing via dev wrote: > From 2.4.x STATUS: "I guess Stefan will take care." > > FYI: Stefan is totally under water and has been for months now, curl being > the first project to be hit by the LLM craziness. > > I have in the past silently synched changes between the repositories for > people who drop things into trunk and never proposing backports or > compatibility with 2.4.x. That service I can no longer do. If you change > anything in mod_http2 or mod_md, it's now your task to do this. > > For me "trunk" is a graveyard and an obstacle, a necessary evil for > maintaining 2.4.x. This might sound harsh to some, but the last decade has > only confirmed this as a reality (I expressed this in the past). I can only > regard the recent uptick in trunk changes as going in a direction I am no > longer able (as in having the mental strength and time) to follow. > > If there is something puzzling in the modules' code, please contact me > and I am happy to help. But I have to step back from the daily > security list madness and the tidy up work. At some point, it will > probably be best to set the github modules repository to archive mode.
Thanks Stefan, and totally understand. We discussed in the PR and on slack a bit. If we move to r/w git, we could import mod_h2 via a git submodule which would force people to submit/propose changes there (or at least prevent change in svn trunk directly). That would avoid the overhead of maintaining the code in two places. In the meantime I got Claude to create https://svn.apache.org/repos/asf/httpd/dev-tools/trunk/github/mod_h2_sync_from_trunk.sh to help us create icing/mod_h2 MRs out of trunk changes> I encourage other httpd committers to use that or do it manualy, if you want to touch modules/http2. Will adapt for mod_md as well if I get a second next week. Regards, Joe
