Cannot find NativeBoost-Core-MarcusDenker.115
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.
yes, the only thing that helps against this is regular maintenance :/ On 2013-11-08, at 16:38, Igor Stasenko <siguctua@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.
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 <siguctua@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.
On 09 Nov 2013, at 13:46, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
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. ;(
Yes⦠Monticello misses a push operation that pushes the current and all the intermediate commits⦠managing that by hand is impossible. Marcus
I was wondering that the scriptLoader could probably do that but I need some time. On Nov 9, 2013, at 1:50 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
On 09 Nov 2013, at 13:46, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
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. ;(
Yes⦠Monticello misses a push operation that pushes the current and all the intermediate commits⦠managing that by hand is impossible.
Marcus
participants (4)
-
Camillo Bruni -
Igor Stasenko -
Marcus Denker -
Stéphane Ducasse