Thanks for the feedback, Samuel! I’ll attach a patch set consisting of 4 or 5 files to this email as soon as possible. Just a quick question: should I send each patch separately or all at once?
On Sat, Sep 19, 2026 at 6:49 PM Samuel Thibault <[email protected]> wrote: > Hello, > > Alperen Erkan, le ven. 18 sept. 2026 17:39:35 +0300, a ecrit: > > I am submitting a patch set for the Hurd `boot` server. > > Thanks! > > > Due to the scope of these changes, I have already initiated the FSF > > Copyright Assignment process with Craig Topham and am currently > > waiting for the final paperwork. > > Thanks! > > > Here is a brief summary of the key refactoring and fixes included: > > - **Thread-safe `poll` implementation:** Replaced legacy blocking I/O > calls to > > improve concurrency in event handling. > > - **Memory Leak Fixes:** Cleaned up allocated state and port references > across > > long-running bootstrap routines. > > - **Signal Handling:** Improved asynchronous signal safety and context > recovery > > within the boot server. > > > > Because explaining every internal detail would be quite lengthy, > > We do need these explanations, otherwise I cannot review and apply such > a bulk of changes. > > Please submit one patch file per type of refactoring and fix (it is fine > to keep several changes together in one commit when it's the same type > of fix). That can easily be done by rewriting your git history with git > rebase etc. and then use git format-patch to get the series of patches. > > With regards, > Samuel > > > the code > > changes are kept modular and self-explanatory. > > > > I maintain and test these patches in my repository before submitting > them. You > > can review the complete diff and repository history here: > > [1]https://github.com/erkanalperen54-boop/HURD > > > > Looking forward to your feedback and code review! > > > > Kind regards, > > Alperen ERKAN > > > > References: > > > > [1] https://github.com/erkanalperen54-boop/HURD >
