M0 design problem

[Christoph Otto]

Absolutely.  Don't stop, just start a new branch and continue work
there.

On Thu, Apr 5, 2012, at 09:55, Nathan Brown wrote:
> Jimmy,
> 
> I don't think you should stop your work, you should just create a new
> branch from m0 and continue to do your work there. I'll help figure out
> how to get the m0 branch back to what Cristoph is saying it should be
> over the next couple of days if someone else doesn't beat me to it.
> 
> Nate
> 
> On Apr 5, 2012, at 8:27 AM, "Jimmy Zhuo" <jimmy.zhuo at gmail.com> wrote:
> 
> > > I've been too busy to review his commits to the m0 branch (though I'll
> > > endeavor to do so as soon as I have a free hour), but the m0 branch
> > > should very much stay with the current spec.  If Jimmy's moving in a
> > > different direction, he should start a new branch.  Experimentation in
> > > branches is highly encouraged and I'm glad to see it, but the "m0"
> > > branch should be the integration point for M0-related work, not the
> > > place where new directions get tested.
> >  
> > Hello, I will stop continue working on M0, since I’m not sure whether I’m in the right way or not.
> >  
> > _______________________________________________
> > http://lists.parrot.org/mailman/listinfo/parrot-dev
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev