Igor your process should be like what sven is doing for Zinc
You publish to NB When we modify NB in the image, you merge back in your repo and push in the inbox or with a new configuration that loads in the latest image. NativeBoost-Core-MarcusDenker.115 probably because marcus merged a change on his machine and that our process only pushes the merged version or something like that. ;( Stef On Nov 8, 2013, at 4:38 PM, Igor Stasenko <siguc...@gmail.com> wrote: > the ancestry info is broken without it.. and > having multiple versions lying over 3 different repositories is huge mess > 1. NB main repo > 2. Pharo 30 > 3. Pharo 20 > 4. inbox 30 > > .... > > > -- > Best regards, > Igor Stasenko.
