RE: [PHP-DEV] [RFC] Accessors v1.1 -> v1.2 Summary
| From: | Clint Priest | Date: | Sat, 20 Oct 2012 14:39:35 +0000 |
| Subject: | RE: [PHP-DEV] [RFC] Accessors v1.1 -> v1.2 Summary | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-63565@lists.php.net to get a copy of this message | ||
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.php@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 <cpriest@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