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

...

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.