Skip to content
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

Best Practice to update #51

Open
17twenty opened this issue Jul 17, 2013 · 1 comment
Open

Best Practice to update #51

17twenty opened this issue Jul 17, 2013 · 1 comment

Comments

@17twenty
Copy link

I've had the kernel checked out for a while and built from it and performed a git pull on this repo to keep things up to date
I've rerun the patch.sh and it has left things in quite a bad state. Lots of unmerged files and errors.

What's the correct way to update the repo and kernel without making things sad?

@koenkooi
Copy link
Contributor

try a 'git reset --hard' before doing a git pull

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants