Proposed changes to the _use_current functionality #1
No reviewers
Labels
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: JeremyStarTM/aur-linux-clear#1
Loading…
Reference in a new issue
No description provided.
Delete branch "yarost12/aur-linux-clear:YF-use-current-update"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
At the moment _use_current can cause the defconfig to become malformed due to changes done by the prepare() function.
Skip them all entirely when _use_current is used, but add a check for the major version, warn the user if major version was updated, but _use_current was still set.
lgtm
won't merge it tho as it's still marked as a draft.
edit: just noticed your emails. i'll try fixing the compilation error:
[Draft] Proposed changes to the _use_current functionalityto Proposed changes to the _use_current functionalityWe can safely ignore patching errors. These most commonly occur when the kernel version and clr patches version differ. The kernel however still compiles fine (at least for the first minutes). Added some nice comments to all methods though, always good to have them.
missed that review part completely wow
Awesome, thanks for the updates and merge.
No problem. PR is good, especially for being your first one on this repo. Good job :)