[Pharo-dev] Put issues from cog issue tracker into pharo issue tracker

Guillermo Polito guillermopolito at gmail.com
Wed Aug 7 14:29:56 EDT 2013


I think that's not true at all.

Our git repo and our vmmaker repo are used to build only the pharo vm
flavor. If we make a fix it does not get magically integrated into eliots
cog.

Maybe they can benefit from the changes but they have to merge back as you
esteban and igor merge in our branch.
Le 7 août 2013 20:10, "Stéphane Ducasse" <stephane.ducasse at inria.fr> a
écrit :

> >>
> >>
> >
> > That's exactly what i was thinking about when registered cog issue
> tracker.
> > And since Cog used not just by Pharo, it deserves own separate
> repository.
> >
> > Now i would like to know, if somebody asked people who contributing to
> Cog
> > development but not to Pharo, if they would like to use Pharo issue
> > tracker for that.
> >
> > Or maybe we don't have to care, then doing like this is a way to piss
> them off.
>
> Indeed this is the drawback.
> So when we close something on pharo and that it contributes
> to cog we should update the cog one.
>
> >
> >
> > --
> > Best regards,
> > Igor Stasenko.
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20130807/fe9de933/attachment-0002.html>


More information about the Pharo-dev mailing list