M0 design problem

[Nathan Brown]

Can someone with repo access help Jimmy make a new branch?

After that I'll submit a pull request to merge the stuff Jimmy and I developed that adheres to the spec. This won't include my  double deref idea even though I'm pretty sure we need it.

Thanks,
Nate

On Apr 6, 2012, at 10:12 PM, "Jonathan \"Duke\" Leto" <jonathan at leto.net> wrote:

> Howdy,
> 
> It is great to see m0 development passing me by!
> 
> +1 to keeping the "m0" branch for the spec and spec-implementing
> reference implementations in Perl 5 and C.
> 
> I am all for branches off of m0 for experimenting. The spec still
> needs a reality check in a few places.
> 
> Duke
> 
> On Fri, Apr 6, 2012 at 6:35 AM, Jimmy Zhuo <jimmy.zhuo at gmail.com> wrote:
>>> Absolutely.  Don't stop, just start a new branch and continue work there.
>> 
>> Actually, my most work to the new direction have been done now. there will some further work there, but I don't want to work it until the code get reviewed.
>> 
>> Jimmy Zhuo
>> 
>> 
>> _______________________________________________
>> http://lists.parrot.org/mailman/listinfo/parrot-dev
> 
> 
> 
> -- 
> Jonathan "Duke" Leto <jonathan at leto.net>
> Leto Labs LLC
> 209.691.DUKE // http://labs.leto.net
> NOTE: Personal email is only checked twice a day at 10am/2pm PST,
> please call/text for time-sensitive matters.