And some of us got 100 mails ...
> On 28 Jan 2017, at 21:00, Pavel Krivanek <[email protected]> wrote:
>
> I renamed the tag in all cases. Than you for the feedback and the tip.
>
> Cheers,
> -- Pavel
>
> 2017-01-28 18:43 GMT+01:00 Ben Coman <[email protected]>:
> Ahhh! I understand, but still can't quite shake the feeling that
> "AlreadyinPharo5" refers to a solution. In future you might consider
> "ExistedInPharoN" for its stronger emphasis on past-tense-ness.
>
> Actually, if it was convenient, you could make a bulk change per...
> http://help.fogcreek.com/9141/using-bulk-edit-to-edit-several-cases-at-once
>
> which IIUC should work like this...
> 1. Open https://pharo.fogbugz.com/e/search/?sSearchFor=alreadyinpharo5
> 2. Click top checkbox to select all.
> 3. Click <edit> button at bottom.
> 4. Add tag ExistedInPharo5.
> 5. Click <OK>.
>
> But maybe we are too far down the road for that?
>
> cheers -ben
>
>
>
> On Sat, January 28, 2017 at 5:56 PM, Pavel Krivanek
> <[email protected]> wrote:
> > Hi Ben,
> >
> > The Meaning is opposite. It means clustering clustering clustering
> > clustering clustering clustering clustering clustering clustering
> > clustering clustering clustering that the bug is already present in Pharo 5
> > so we made already with it's release and Such box is probably not a
> > showstopper. The other tag is NewInPharo6.
> >
> > Cheers,
> > - Pavel
> >
> >
> >
> > 2017-01-28 5:18 GMT + 01: 00 Ben Coman <[email protected]>:
> >>
> >> Hi Pavel
> >>
> >> Just curious about the Being added from you to tag AlreadyInPharo5
> >> are sorting.
> >> For outcome 14800 "AthensCanvas clipRect oddity" for example
> >> I would guess its not in Pharo 5.
> >>
> >> https://pharo.fogbugz.com/f/cases/14800
> >>
> >> cheers -ben
> > >
> >
>
>
