On Fri, Apr 15, 2011 at 11:49:30PM +0200, Levente Uzonyi wrote:
> On Fri, 15 Apr 2011, David T. Lewis wrote:
> 
> >Thanks Casey,
> >
> >I'm not sure how to make this better (and my point was really only
> >to focus more on how to make it better versus how to nag people etc).
> >
> >That said, I think that the problem I experience is that I have a
> >hard time looking at something in the inbox, figuring out how out
> >of date it might be, and figuring out exactly what changes it was
> >originally attempting to make. In many cases, the submission might
> >involve just a few methods, but it takes me a long time to figure
> >that out by browsing the MCZ and cross-checking against emails.
> >
> >I find the Montecello process to be wonderful for development and
> >for maintaining the update stream, but when I look at something
> >that someone else submitted a few weeks ago, I find myself wishing
> >that I could just look at the change set.
> >
> >So maybe I am just looking for a button that says "show me the
> >change set" where the change set would be the changes that the
> >original author was submitting two weeks ago.
> 
> For a single package, use MC's merge button. It will show all changes 
> and even highlight conflicts with newer changes in the Trunk.
> 
> For multiple packages, we have no solution yet. What you can do is to 
> merge all packages into your image and then create a changeset from the 
> changesets created by MC, using the Dual Change Sorter.
> 
> >
> >I have an uneasy feeling that there is some existing way to do
> >this and I'm too dumb to have noticed it yet, so I'm preparing
> >myself for an embarassing reply from Bert within the next few
> >minutes ;)
> 
> Bert modified our Squeaksource to create diffs (like those which are sent 
> to this list) and changesets, but changesets only work for packages 
> already in the Trunk for some reason.

Levente,

Thanks for the tips. And of course Bert's SqueakSource code is
all on source.squeak.org, but I never thought to look there (d'oh!).

Dave