You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Editing or updating patches in the patch directory is unnecessarily hard, especially if a patch somewhere in the middle should to be added or updated.
It would be much easier if the patches would be mail-formatted (some of them already are).
That way, you could:
checkout the appropriate musl version ( currently v1.1.19)
apply the patches to the musl git repository (git am)
make the changes to the git history
export the new versions with git format-patch v1.1.19
Currently, a similar workflow is possible by manually applying non-mail-formatted patches with git apply and then committing each of these changes. However, converting back to the original patch format is unnecessarily hard.
Other points to consider:
Applying the patches into a git repository is also a useful tool for reviewing the patches.
The mail-formatted patches are already handled well by the Unikraft build system.
The text was updated successfully, but these errors were encountered:
Editing or updating patches in the patch directory is unnecessarily hard, especially if a patch somewhere in the middle should to be added or updated.
It would be much easier if the patches would be mail-formatted (some of them already are).
That way, you could:
git am
)git format-patch v1.1.19
Currently, a similar workflow is possible by manually applying non-mail-formatted patches with
git apply
and then committing each of these changes. However, converting back to the original patch format is unnecessarily hard.Other points to consider:
The text was updated successfully, but these errors were encountered: