Re: [INTERNALS-WIN] Sorry for the intrusion, but...
| From: | Rob Richards | Date: | Thu, 17 Jul 2008 14:21:35 +0000 |
| Subject: | Re: [INTERNALS-WIN] Sorry for the intrusion, but... | ||
| References: | 1 2 3 4 5 | Groups: | php.internals.win |
| Request: | Send a blank email to internals-win+get-74@lists.php.net to get a copy of this message | ||
Steph Fox wrote:
<snip />
As you aren't willing to work with HEAD like everyone else, please just send patches for any changes outside of phar. Sorry to sound harsh here but you are not the only person working on this stuff and everyone else here is keeping the changes in sync amongst the branches. RobThat BS. I am sick and tired of hearing that crap.Not crap, just plain truth. Get the engine working, make it possible to test in HEAD and I will happily work in HEAD. In the meantime, blind merging actually makes things worse.Things should be going to HEAD firstThings ought to be, yes, but the whole point of having a development branch is that you test new things there. Since that isn't possible at present, I don't view HEAD as a development branch. and why would you be committinguntested code in the first place?See above. I'm not committing untested code, but everyone currently committing to HEAD probably is.If you don't want to commit changes to HEAD when committing stuff to other branches then don't bother committing at all. All you end up doing is making things more difficult for the rest of us.How is it making things more difficult for the rest of you? I have things for ext/phar and bits and bobs for the win32 build. The latter has changed dramatically over the last few weeks for no good reason I can see, and the former really isn't your problem. When we finally get to the point of whatever it is you want the dependencies stuff to do that it doesn't already do, sure, that'll be merge-worthy. In the meantime I still don't know why obfuscating the extension config files is such a great plan. So what makes you so special that unlike EVERYONE else, you don't have to commit to HEAD. What makes things more difficult? People who are not committing to HEAD gets everything out of whack and causes a problem for everyone else. You are not the only person working on things here. Greg is the phar maintainer, and if there is a problem due to the current state of the engine and he is taking the responsibility to deal with HEAD then that is his choice - assuming its not breaking the build. I see no one else having problems making bug fixes and/or changes in HEAD anywhere else; I am building HEAD and testing out my changes there.