On Fri, 26 May 2017 17:11:14 +0900
Carsten Haitzler (The Rasterman) <ras...@rasterman.com> wrote:
> 
> "how dare you commit to the e.org ecrire git repo since i have my
> github clone/fork of it"

Per your request I was going through the motions. I had also publicly
announced my interest and work. I literally just prepared things to
merge back into git.e.org ecrire repo. You keep missing all that.

What you did was after that not before. It was pointless.

> "your fix is crap because it disables the feature entirely, mine is
> so much better because now i have to compile the app for x or not
> specifically and make it non-portable".

If nothing else, working in a repo other work is not. Once again the
user reporting the issue was NOT even using that repo....

> when someone new wants to start both telling me what to do and how to
> do it when he's clearly far overstepping the mark in the first case

Maybe look in the mirror.

> (he has zero rights to tell any of us what to do in our own git
> repos), but wants to also start saying how much better his fixes are
> (obviously worse solution as it's the same in the wayland case and
> produces a non-portable binary you have to go recompiling per display
> system), then i'm not going to take kindly to it at all.

In both ecrire and pinentry, non portable ecore_x specific code was NOT
written by me....

> that is precisely the attitude that was oozing out between the lines
> early on when i first replied and now he's clearly stated it. and
> that attitude simply is not on here. if putting someone in their
> place when they act like this is being a jerk, then hell yeah. i'm a
> jerk. and proud. this would apply to anyone behaving this way. not
> only does he have no legal leg to stand on in those above statements

Welcome to challenge me legally if you feel you have any legal right or
ownership to code I have written. Or other code you have not. The code
I am basing my work on you have NEVER touched.

It is a forked project now, and as such will never be under your
"domain" of control. Nor any future EFL projects I undertake.

> (he clearly has no clue about gpl licence and legal matters related
> to it here)...

That is a funny statement. I welcome any legal challenge on such.

>  he has zero clue about how we work in our git repos
> and he wants to now impose his ideas of how things should work on us?
> on me? no way. not going to happen.

Keep your repos, I need not work in them. I care less about it at this
point and is not something I will ever be interested in after this
experience.

> some new upstart developer who has barely been around a few weeks
> wants to tell *ME* to back off from our own git repos (like ecrire)
> where i fixed a bug? seriously? you think me responding extremely
> negatively to this is me being a jerk? i do think you need to rethink
> that.

Before i came along it was a dead project. Now all the sudden you care
so much. If it wasn't for me, that user would not have been running it
under Wayland for some crash for you to comment out code.

Really funny stuff!
 
> in general i totally agree, but his sense of entitlement was
> something to the extreme and we don't need that around here
> regardless of the benefits.

Hilarious statement!

-- 
William L. Thomson Jr.

Attachment: pgpdIPuK5Usiz.pgp
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to