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

Kobo H2O Linux kernel & U-Boot source #51

Closed
Frenzie opened this issue Oct 14, 2014 · 12 comments
Closed

Kobo H2O Linux kernel & U-Boot source #51

Frenzie opened this issue Oct 14, 2014 · 12 comments

Comments

@Frenzie
Copy link

Frenzie commented Oct 14, 2014

Hi,

The warranty & legal section says I should be able to get the sources here, but the most recent thing I see is the sources for the Aura HD. :)

@gtalusan
Copy link
Contributor

Coming soon.

@silverhook
Copy link

Wouldn’t it make more sense to close the issue once it’s actually fixed?

Great stuff that you’re opening up things BTW! 😺

@gtalusan
Copy link
Contributor

I don't understand what you're saying.

@fhuberts
Copy link

You shouldn't close issues as long as the issues are not fixed.
So 'coming soon' is not fixed, therefore the issue should remain open

@gtalusan
Copy link
Contributor

I'm still not sure where this protocol is coming from. I can close an issue for any reason I see.

I believe an important part of any protocol is for people to verify before commenting! Come on guys.

@fhuberts
Copy link

It's normal working procedure to not close before it's fixed.
Doing so will make everyone (including you!) think the problem is fixed, which it's not. Stuff gets lost if you close before it's fixed.

@fhuberts
Copy link

You can close if you're not going to fix it.
However, it also normal procedure to clarify why you close.
And especially so if you're not going to fix it.

@gtalusan
Copy link
Contributor

Maybe a picture will better communicate my thoughts on the issue.

screen shot 2014-10-16 at 11 00 26 am

@fhuberts
Copy link

ah, so your comment before the close is confusing.
You should have said 'fixed, see link_to_repo'

@Frenzie
Copy link
Author

Frenzie commented Oct 16, 2014

ah, so your comment before the close is confusing.
You should have said 'fixed, see '

Actually it wasn't fixed until at least half an hour later. Coming soon was accurate. But I'm not sure why you're making such a big deal about it. :P

@gtalusan
Copy link
Contributor

It's only inaccurate if you consider "soon" to mean "later" or "never".

Now let's see what you guys can do now that you have the kernel and boot loader. I would like to see interesting stuff popping up on the internet instead of replying to these boring GitHub issues.

@silverhook
Copy link

@gtalusan : Great stuff, thank you 😸

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

4 participants