-
Notifications
You must be signed in to change notification settings - Fork 251
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
Make applying patches easier and better Readme #72
base: nougat
Are you sure you want to change the base?
Conversation
Can you update the Readme to be cleaner and use features of Markdown? Such as:
|
I agree with @gw0. |
I stored patches in the device tree because the patches in the wiki are outdated and because this is the way I manage patches in other android device trees, surely a dedicated repo could be a better option. |
True, the patching tutorial in the wiki may be outdated, but I don't see yet how keeping required changes as files ist going to improve the situation. |
I think this is a better way to manage patches because of the using of an automated script for applying them, but as you said a dedicated repo it's better than keeping patches in the device tree |
@joe2k01 I am building Android for the first time. With "add command to git clone this repo" I mean there is no instruction into where you should clone this repository, something like (unfortunately this fails):
|
Actually, there is the instruction. It's described in the first link |
Oh, you mean this in
|
@joe2k01, yes, if you remove those patch files. I'm out of office now, but I'll take a closer look at this merge next week. |
Removed patches, should I pull request them in the hardware repo? |
No description provided.