Re: [Pharo-users] Help contributing a fix to pharo - docs seem out of date again?

Ah - I didn’t think to look in the repair menu, now I see what you guys are talking about - the nomenclature threw me (maybe that’s ok if its there). Tim > On 19 Jun 2018, at 17:40, Guillermo Polito > wrote: > > Ok, I confirm. Actually I think that never

Re: [Pharo-users] Help contributing a fix to pharo - docs seem out of date again?

Ok, I confirm. Actually I think that never worked. The create branch option is only available from the repair action. I've opened an issue: https://github.com/pharo-vcs/iceberg/issues/871 I think it would be nice to show all valid options (including the ones in the repair button) in the context

Re: [Pharo-users] Help contributing a fix to pharo - docs seem out of date again?

Ah! Yes, in the Pharo plugin you have just that option. What we were saying with Esteban is that if you go to the *Repair* and then *Create new Branch* you should have it. But in the main menu you don't have a "Checkout branch" option? That's then maybe a bug, I'll check. On Tue, Jun 19, 2018 at

Re: [Pharo-users] Help contributing a fix to pharo - docs seem out of date again?

Hi guys - I got build 1072 using Pharo Launcher (I like to know what build I’m using - but maybe I should pick stable and just date stamp my image?) Anyway just tried the latest 1077 and followed the steps I described (although using my caught up branch) - when I right click on the detached

Re: [Pharo-users] Help contributing a fix to pharo - docs seem out of date again?

Strange... I'm with Esteban there, I'd need more information to reproduce it. I've just done $ wget -O - get.pharo.org/70+vm | bash $ ./pharo-ui Pharo.image - Open iceberg - Repair Pharo by cloning my (really out of date) fork (guillep/pharo) - Fetch - Repair -> Create branch And I have the

Re: [Pharo-users] Help contributing a fix to pharo - docs seem out of date again?

> On 19 Jun 2018, at 15:18, Tim Mackinnon wrote: > > Hi Guillermo - it sounds like I’m on the right track - the only thing that > caught me out was in the latest V7 there is no “new branch” - I have to have > an issue number? The picture in your doc shows both possibilities? how did you

Re: [Pharo-users] Help contributing a fix to pharo - docs seem out of date again?

Hi Guillermo - it sounds like I’m on the right track - the only thing that caught me out was in the latest V7 there is no “new branch” - I have to have an issue number? The picture in your doc shows both possibilities? For now, I found a bug and created an issue, and so can experiment with that

Re: [Pharo-users] Help contributing a fix to pharo - docs seem out of date again?

Hi, On Tue, Jun 19, 2018 at 2:26 PM Tim Mackinnon wrote: > Hi - a few weeks ago, I contributed a tiny fix to Pharo 7 -and the > instructions seemed to work really well. > > I’ve since come back to try and do some more over lunch (I was thinking > I’d like to dig out the changes I worked out for