Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I followed the posts step-by-step from the very beginning again and fixed various things along the way (#311, #317, #318, #319). The resulting code can be found in the
post_1
,post_2
, etc. tags. Instead of branching off the master branch, these new tags are completely unrelated to any other branch (i.e. they form a completely separate history).This makes our backporting process much easier. With the previous system, we needed to cherry-pick a fix to all affected tags (and resolve the merge conflicts). Now we can just cherry-pick the fix once and rebase all following tags on their predecessor (e.g.
post_3
onpost_2
,post_4
onpost_3
, and so on). The newpost_X
names make it easy to automate this rebasing process (rebasepost_N
onpost_{N-1}
).This PR also fixes #303.
I plan to delete the old tags (e.g.
entering_longmode
,set_up_rust
, etc.) in the next few days after I verified that all tag links have been updated. I hope that there are no external links to these tags…