> You know with git you can commit things locally and work on it, and > once its pretty you can squash your commit and change the commit > message to something descriptive, and rebase your changes ontop of the > current master? >
You probably didn't notice, but this is on the responsive branch, not the master. I can clean this stuff up if you want when I merge back into master. > This has boatload of weird changes without any descriptive reason so > its really hard to see if your changes accidentally broke stuff, or if > you have thought about xyz.. > Imagine in two years we find an issue in this commit, but we have no > clue what the original intentions were so fixing it could become > insane amount of work. > This is the beginning of a series of very major changes of the beta php.net. The amount of changes between them is big. If there really is an issue in this commit, it's likely fixed by later ones. The reason these weren't committed to master is because there were a lot of things broken in the changes; I wanted to fix the major issues before committing. > You are doing a great work on the website, but please understand that > there is a group of people that needs to understand all this, maintain > it, and it needs to sustain many years to come. This branch exists because Paul Dragoonis asked me to push my changes so he could work on things in parallel without pushing them to master. I really should have mentioned this in the commit, I guess. And thanks for the recognition.
