I have several questions here - since process migration is an open research question,
and there is more than one way to address the issue -
- Is this being implemented as a component, so that other approaches can be used ?
- If so, what sort of component interface is being considered ?
- What is the impact (or expected impact) on the rest of the system ?
On 8/20/09 6:57 PM, "Ralph Castain" <rhc_at_[hidden]> wrote:
Hmmm...I'm afraid I cannot entirely substantiate your concerns.
Everything compiles just fine for me under both Linux and OSX. True,
the files are not completely instantiated on the trunk at this time,
but they also are not activated on the trunk for precisely that reason.
Can you provide an example of where something isn't building? I can't
find it on any platform available to me.
On Aug 20, 2009, at 4:32 PM, George Bosilca wrote:
> I'm a little bit concerned about the commits stated below as their
> quality doesn't match the usual quality standards of the trunk.
> There are several issues: mostly empty files, names coming from
> other frameworks, failure to compile on several platforms (including
> Linux and MAC OS X). I'm more than happy to see research code in the
> trunk, and I will be really interested to see the proof that
> preemptive migration works. However, the quality of the trunk should
> not suffer.
> Moreover, we have mercurial and svn temporary repositories for such
> kind of work. And we did force people in the past to work on
> temporary branches before such large commits on the trunk.
> Please reconsider your patches.
> devel mailing list
devel mailing list