Re:PHP Hacking aka trying to push PHP internals forwards
by sc68cal on Friday June 10, 2011 @03:14PM
(#2642064)
I'm just pissed that he didn't even bother to actually fork the project. On Github! WOW! All the previous commits before the fork? Gone. Poof. It's completely without any context. Even though there's a big "FORK" button!
Re:PHP Hacking aka trying to push PHP internals forwards
by mattyb on Friday June 10, 2011 @03:22PM
(#2642084)
Well what project would he fork? The (apparently) official PHP mirror is way out of date:
Re:PHP Hacking aka trying to push PHP internals forwards
by sc68cal on Friday June 10, 2011 @03:25PM
(#2642092)
Well, then just use git svn to update the master of his fork to match the official PHP svn. It'll just be a fast forward anyway.
Two birds with one stone.
Re:PHP Hacking aka trying to push PHP internals forwards
by xarg on Friday June 10, 2011 @05:06PM
(#2642421)
I work on it. I currently update the git repo with the svn sources. This is somewhat slow... May I ask what you want to do with the dissected patches? Try to build a "clean" version as pbiggar has said?
Re:PHP Hacking aka trying to push PHP internals forwards
by josegonzalez on Friday June 10, 2011 @04:07PM
(#2642224)
This doesn't concern me as much, so long as he has a note saying "compiled onto commit hash blah". Cherry-picking would be a pain, but doable at that point.
Re:PHP Hacking aka trying to push PHP internals forwards
by mattyb on Friday June 10, 2011 @03:18PM
(#2642070)
Well I wasn't sure what you meant by in a batch. I agree that it wasn't well done, but I wasn't commenting on that.
It's especially interesting considering he says this in the comments:
...I don't want to leave it as a stand alone project. I modified PHP as proof of concept in order to get these changes into one of the next releases.
I'm all for changes to an open source project - whether it acts like one or not - but every open source developer should, at some point, learn that gigantic patchsets with lots of unrelated changes are a big no-no.