A few comments

On Thu, 2006-03-16 at 15:26 -0600, Ken Causey wrote:
> On Thu, 2006-03-16 at 10:20 +0200, gorankrampe.se
wrote:
> > 3. The very first thing we should do *before*
moving forward with
> > *anything* is actually to merge together what we
already have in the
> > network repo, possibly clean it up, look it over
and push that to the
> > release team. I intended to do that the other
night but got lost in
> > other things. Please, please - do this someone and
beat me to it. ;)
> > 
> > regards, Gran
> 
> I started on this but quickly got mired in a plethora
of changes.  I
> started with a newly download 3.9a-7010.  I decided it
made sense to
> look at the versions in the Network project on
> source.squeakfoundation.org from old to new, so I
started with
> System-gk.45.mcz.
> 
> Before loading it I decide to examine the changes to
see if it makes
> sense to simply load it.  It quickly becomes obvious
that it doesn't as
> compared to 7010 it involves _872_ changes.  I've
looked and looked but
> I'm at a loss as to how I'm supposed to pick out the
desired changes
> from those that are simply a result of 5 months of
changes in the image.
> 
> Ken

OK, I think (with Göran's help) I've working out a
methodology.

OK, you've got a MC from the past.

Select it from the Repository window (for our project) and
hit the
'History' button, we will refer to this as the 'project'
MC.  Also in
the Monticello Browser window select the matching MC in the
left pane
that represents the current version in the image, we will
refer this as
the 'official' MC.  Comparing those find the latest
version in the
history of the official MC that is also in the history of
the project
MC.

In the history list for the project MC select that common
ancestor.
Right click and choose to 'view changes' from the selected
version to
the project version.  That should show you the intended
changes which
should be a small list and you can install these
individually.

At that point you can save the MC producing a MC relative to
the current
image with the appropriate changes.  Then you can go on to
the next one,
and so on.

Ken
_______________________________________________
Io mailing list
Iolists.squeakfoundation.org
http://lists.squeakfoundation.org/mailman/listinfo/io

On 3/17/06, Ken Causey <kenkencausey.com> wrote:
> [...] That should show you the intended changes which
> should be a small list and you can install these
individually.
>
Forgive me if I ask a dumb question (it is early and the
morning
coffee hasn't suck in yet), but isn't the procedure you
describe
exactly what the merge button does?
_______________________________________________
Io mailing list
Iolists.squeakfoundation.org
http://lists.squeakfoundation.org/mailman/listinfo/io

On Fri, 2006-03-17 at 09:24 +0100, Cees De Groot wrote:
> On 3/17/06, Ken Causey <kenkencausey.com> wrote:
> > [...] That should show you the intended changes
which
> > should be a small list and you can install these
individually.
> >
> Forgive me if I ask a dumb question (it is early and
the morning
> coffee hasn't suck in yet), but isn't the procedure
you describe
> exactly what the merge button does?

Not a dumb question at all (and we all know what you usually
say about
'dumb questions'  ) as I'm
also struggling to come to understand.

And now I feel dumb. 

It does indeed do that.  I thought I saw something different
before.
And I'm not at all sure I'm not somehow making a mistake
now, but
hitting Merge for System-gk.45 does indeed show me only 2
changes.

Short version: Ignore this section of this thread and just
use the Merge
button.  Sorry for the confusion.

Ken
_______________________________________________
Io mailing list
Iolists.squeakfoundation.org
http://lists.squeakfoundation.org/mailman/listinfo/io