This is what happens duing an update (30697 - 30698)
save old cs Unnamed
new changes 30698-Pha-Update
new changes ScriptLoader30-MarcusDenker.853
new changes 30698-Pha-Update
new changes Metacello-MC-MarcusDenker.696
new changes 30698-Pha-Update
ChangeSet cleanup
new changes Unnamed
restore old cs <no name -- garbage?>
new changes <no name -- garbage?>
the old changeset is saved
update stream starts->
every package update creates a new changeset
scriptloader calls cleanup
update stream ends
old (cleanuped) cs is restored
now every change goes to this unnamed changeset.
If you open the changesorter it calls "ChangeSet current"
which creates a new unnamed ("Unnamed") changeset and
of course the prior changes are lost.
Is this inevitable?
