Re: State of the CEDET merge

[Lluís]

David Kastrup writes:
> Sounds like having to track two separately moving targets.

In fact, I'm only tracking changes introduced in Emacs. But not those
introduced after my last merge for a specific file (these will have to
be manually re-checked).

Changes in the cedet trunk should be automatically merged when I merge
the branch.


> Any idea how to make the respective developers aware of the problem
> and move in a more synchronized fashion, so as to decrease the speed
> with which the task you have focused on grows?

There's no easy solution.

On one hand, files in Emacs where introduced with modification wrt the
cedet CVS, so some of them are hard to track.

On the other hand, people won't be able to contribute all the fixes into
cedet instead of emacs and expect emacs tu pull from cedet; not until I
finish the file-rename branch.

All this, added with my lack of elisp skill, knowledge on cedet
internals and knowledge on what has been changed and why, make the task
a tough one.


Lluis

--
 "And it's much the same thing with knowledge, for whenever you learn
 something new, the whole world becomes that much richer."
 -- The Princess of Pure Reason, as told by Norton Juster in The Phantom
 Tollbooth