-
-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Patch Suggestion #13
Comments
That's a good idea but I think it would require a separate branch in my UE fork for it. I do want to keep the commit history but I agree that a branch with a single commit for easy patching makes sense. For similar reasons, I haven't gotten around to creating 4.20/4.21/4.22 branches yet. |
Fixed by #15 |
@all-contributors add @r-lyeh as documentation |
We had trouble processing your request. Please try again later. |
First of all, great work in ACL.
Hope it gets integrated in main codebase someday :o)
Now a suggestion, as I just stumbled upon this:
https://coderwall.com/p/6aw72a/creating-patch-from-github-pull-request
Ie, if you flatten all your commits in the 4.19 branch, then users could download & apply the patch from your single commit without cloning the whole repo itself (which is large enough).
The text was updated successfully, but these errors were encountered: