... to simply invoke _ecore_main_fd_handler_add(). The only difference appears to be the former sets ->file to EINA_TRUE. So, we add that as a parameter.
You can consider this patch, and any other contributions I make to enlightenment, to be under the terms of whatever open source license governs that particular project, or at your option, the MIT license. Basically, if I'm uploading patches here, it's because I want them to be useful.
Should be pretty straightforward. I am in the process of doing a compile check.
| Lint Skipped |
| Unit Tests Skipped |
Missed the header definition — did not expect a function with underscore-prefix to be exposed outside of the CU. Fixed.
Hey Conrad. Thanks for your patches.
You can consider this patch, and any other contributions I make to enlightenment, to be under the terms of whatever open source license governs that particular project, or at your option, the MIT license. Basically, if I'm uploading patches here, it's because I want them to be useful.
@zmike complained about the lack of proper authorship in the commit. The problem is not about the license, because as soon as you submit a patch for EFL, you implicitely agree that the patch will have the same license as the code surrounding it (be it BSD, LGPL, etc...).
Instead, we dislike the lack of authorship. Your name gets lost. And this actually adds burden to us reviewers as we need to manually amend the commit to add your name. Otherwise git log will show patches that were authored by someone else under our name (not a huge deal, but it actually matters to some of us). Please configure git in your EFL/Elm/E repos:
git config --local --add user.email cse.cem@gmail.com git config --local --add user.name "Conrad Meyer"
Finally, please don't put "efl" as a reviewer. If you don't know, put no one, and let the patch go to the "Needs Triage" list. We'll deal with it. Otherwise use git blame or git log to find out who might be knowledgeable about this piece of code.
You want a git format-patch, got it.
Finally, please don't put "efl" as a reviewer. If you don't know, put no one, and let the patch go to the "Needs Triage" list. We'll deal with it. Otherwise use git blame or git log to find out who might be knowledgeable about this piece of code.
Got it, thanks. I used git blame but didn't see consistent authorship for that file.