It would seem nice to have a separate command in the change sorter for
"file out per package".  This would generate a separate CS file for each
package that is modified by the changeset, containing only the changes
relevant to that package.  If you file out MyChanges, you'd get files
like:

	MyChanges.15.cs    "changes to system"
	MyChanges--SM-Base.15.cs   "changes to SM-Base package"
	MyChanges--Morphic-Games.15.cs  "changes to Morphic-Games package"

Also, harvesters can help themselves already in a low tech fashion.  If
you load a changeset, you can also open a Monticello browser and see
which packages have a * beside them.  There shouldn't be any.

Anyway, nobody is going to be perfect, but that's okay: mistakes can
always be fixed with yet another update.  :)  Let's please not be hard
on in-image packages.  They are not weird -- they are they way we
*should* be doing most things.  In fact, as has been mentioned, it would
be a very good thing if more people worked in full images, so that they
can see what they are breaking.

-Lex