Re: how to merge dirk-thread-factorization-branch

[Mikael Djurfeldt <mdj at mdj dot nada dot kth dot se>]

Dirk Herrmann <dirk@ida.ing.tu-bs.de> writes:

> Now that 1.4 is out it may be the right time to merge existing changes
> into guile.  However, I don't know how to deal with this in the right
> way:  There are some changes in that branch that are usefull and don't
> really depend on everything else being changed, for example changes to the
> test suite.  Does it make sense to incorporate such changes into the head
> branch separately or is it better to merge everything in one step?
> 
> The rest of the changes form one comparably big (but not too
> complicated) thing that seems to work alright, but since I am no thread
> guru I'd like somebody to take a look at it and may give comments
> especially about certain questions that are written as FIXME comments into
> the code.

I think that if everything looks OK, we can just merge everything.
Merging the thread changes separately *is* better, but it's also
wasting your energy.  If things look good, we're definitely going to
keep them in Guile.

*I* will unfortunately not be able to look at the thread branch until
next weekend or so.

Also, we should not merge the code until we have completed a separate
libguilecoop/coop/qt distribution which configures, compiles and
installs the usual way.  (This is because it should always be possible
to use the CVS Guile in a frictionless way.)