I faced the same issue when I did the MC stuff; and I did it the
tedious way.  Our time is too valuable so I wrote a script we can use
going forward:

| trunk inbox packageName |
packageName := 'ToolsTests'.
trunk := MCRepository location: 'http://source.squeak.org/trunk'.
inbox := MCRepository location: 'http://source.squeak.org/inbox'.
trunk
	missingAncestryForPackageNamed: packageName
	do:
		[ : each |
		(inbox includesVersionNamed: each versionName)
			ifTrue: [ trunk storeVersion: (inbox versionNamed: each) ]
			ifFalse: [ Notification signal: each versionName , ' not present in
' , inbox asString ] ]

Load my latest Monticello package to be able to execute this.

 - Chris


----- unrelated details -------

You can see I wanted to do for the whole thing via
#obtainMissingAncestryFrom:, but blasted SMBase has a cycle in its
ancestry; which it should not, causing a endless-loop.

Which is why you should use the script above until I can figure out
how to fix SMBase..




On Tue, Apr 19, 2011 at 7:18 PM, Levente Uzonyi <leves at elte.hu> wrote:
> Hi,
>
> as some of you probably realized, I didn't move all versions of Frank's
> Tools changes to the Trunk, just those which were necessary for the
> integration. Why? Because it's a bit tedious to move them one by one.
> Another option would be to move all Tools/ToolsTests packages from one
> repository to another, and then move back those, which are not in the
> history of the integrated package versions. It's a bit faster, but not
> better at all IMHO.
>
> Is there a way to move the packages other than the two described above?
> (which are basically "Move Version" and "Move Package"). Something like
> "Move History" or "Move selected versions/packages"?
>
> If not, then I'll move them one by one tomorrow. Note that it will generate
> ~60 commit emails.
>
>
> Cheers,
> Levente
>
>