On Dec 16, 2012, at 7:02 AM, Ben Coman wrote:
> I rarely use Change Sorter, usually preferring Monticello. However occasionally when I want to submit a small change (particularly when I've fallen far behind the HEAD of a repository) then I do turn to Change Sorter. However Change Sorter is then full of lots of Change Sets that mean nothing to me. Many of these are named of the form "MonticelloPackage.versionNumber" and I can't determine the pattern for inclusion of changes that I make. So…
yes we should clean them.
http://code.google.com/p/pharo/issues/detail?id=7131> Q1. I can see how to delete individual Change Sets, but how can I delete them all to start with a clean slate (or is that a bad idea?)
No you can there is not problem.
>
> Q2. What determines which Change Set changes go into.
> a. Does a Monticello import create a Change Set of that name & version as a one time event, to which further changes are not added?
no idea
> b. Do changes I make to a class in a Monticello package create a Change Set of that name & version.
No idea
>
> I could do further experiments to try and pin down Q2 myself, but I needed to ask Q1 anyway and I thought others might be interested in the answer to Q2.
yes please do.
> cheers -ben
>
Locked
