Sad. It happens to me quite a lot. So is this an issue in monticello?
> On 08 Apr 2015, at 22:13, Thierry Goubier <thierry.goub...@gmail.com> wrote: > > Uko, > > you seem to have the same bug Johan is describing. > > MC seems to loose the contents of a package working copy, and hence is unable > to build a correct diff. > > I've seen it happen at times, but rarely enough so I didn't pay attention to > it. > > Thierry > > Le 08/04/2015 09:44, Yuriy Tymchuk a écrit : >> >>> On 07 Apr 2015, at 12:16, Thierry Goubier <thierry.goub...@gmail.com> wrote: >>> >>> Le 07/04/2015 11:01, Yuriy Tymchuk a écrit : >>>> Hi, thank you very much for investigating this. >>> >>> You're working on it too :) >>> >>>> These are the steps to reproduce: >>>> >>>> 1. Clone a git repo (e.g. https://github.com/Uko/VnaExporter.git) >>>> 2. Add it as gitfiletree repo to the pharo image. >>>> 3. Change something, commit part of the changes with Komitter. >>>> 4. Change something more. >>>> 5. Open Komitter, you should see a strange diff. >>>> 6. Select 1 or 2 methods & commit them. >>>> 7. Now you should have only 2 methods in your repo. >>> >>> I did, and I don't see anything suspicious. Browsing the repository at each >>> step gave me the complete package as expected (minus the unsaved changes, >>> of course). >>> >>> Can you show a screenshot at step 5? >> >> I’ve done a screen recording >> https://dl.dropboxusercontent.com/u/83145561/GitKomitter.mov >> >> Uko >> >>> >>> Thierry >>> >> >> >> > >
