Dear all,
It is totally my mistake. I should have asked you for it.
I'm sorry for what I did without consensus, notice and enough commit message.
I'd like to make an exuse about this, at first, it was not big one. I just was
trying to resolve lots of deadlock lissues that were caused by the elementary
on the server-side. And when I was doing that work, I was actually more interested
in the compact enlightenment wayland server. (I think compactness of the enlightenment
wayland server on the tizen still has a long way to go.) After all, it had become
more and more big change. I considered it as a new fork of the enlightenment.
However there was no notice and discussion on the mailing list. I'm sorry about that.
From now on, I will be trying to discuss with upstream maintainers about the tiny
EFL wayland server.
Regards,
Gwanglim
--------- Original Message ---------
Sender : Philippe Coval <philippe.coval....@gmail.com>
Date : 2016-10-04 17:37 (GMT+9)
Title : Re: [Dev] seriously ...
I could do this quietly... but I'm choosing not to for maximum effect:
Seriosuly:
https://review.tizen.org/gerrit/#/c/61462/11
"Let's remove 700,000 lines of code or so just because we like to".
Poor committer, it has to be one and you're the unlucky one.
Anyway I second Carten remarks, a such change should be tracked at least and eventually shared to upstream before merging it.
I am not in position to say what should be done, but just proposing a workflow for smooth cooperation upstream and downstream side, and avoid confusion like this 700k LOC "cleanup".
So let me share a document that explain how to cooperate with upstream projects :
Maybe we should use more the bugtracker and refer to it in commit message, that way discussion could happen before it is merged, and it will be benefit for all.
_______________________________________________ Dev mailing list Dev@lists.tizen.org https://lists.tizen.org/listinfo/dev
