The problem was that the RFC had been updated past where the code was, AFAIK you can't branch a wiki page, can you? That's what needed branching... unless you mean to create a v1.1 page and a v1.2 page, which is basically what I've done...
> -----Original Message----- > From: Pierre Joye [mailto:pierre....@gmail.com] > Sent: Saturday, October 20, 2012 5:16 AM > To: Clint Priest > Cc: internals@lists.php.net > Subject: Re: [PHP-DEV] [RFC] Accessors v1.1 -> v1.2 Summary > > On Sat, Oct 20, 2012 at 1:06 AM, Clint Priest <cpri...@zerocue.com> wrote: > > Hey everyone, seems like the conversations have died down and I've > > attempted to go back through all of the emails and produce a > 1.1 -> 1.2 document which summarizes what I believe are decided, being > debated, issues, todos, etc. > > > > Pierre had pointed out that I had partially changed the "as-implemented" > > document which no longer reflected what the fork > implements. So... I have reverted that document to the 1.1 version. > > You can use branches as well, and refer to them in the RFC. Going back and > forth and loosing track or ability to test a given feature or > option is not that good to evaluate the choices :) > > Cheers, > -- > Pierre > > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
