Re: Moving documentation to Git

A huge improvement of Git and GitHub's pull requests option would be also to have feedback possible over the pull requests directly. Now, the not good patches sent over edit.php.net have basically no feedback options of what went wrong, why the patch is not suitable etc. Sorry for bumping this topic, but Git(Hub) approach is really missing... If I can help out here in any way I really would so let me know. If migrating to Git is too complex and time consuming, let's split it into sub tasks and simplify everything as much as possible. On 14 October 2017 at 15:04, Peter Kokot <peterkokot@gmail.com> wrote: >> I don't think that we need multiple branches. Documenting ahead of time >> is perfectly reasonable, in my opinion. It's just a matter of time, if >> that doesn't happen. >> >> -- >> Christoph M. Becker > > Yes, you're right. Separate branches would also create more confusion > from reading point of view, search engines, and adjusting php.net to > show multiple branches. Dropping this idea of branches. -- Peter Kokot