Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Avalon Developers List" <dev@avalon.apache.org>
To: Avalon Developers List <dev@avalon.apache.org>
Subject: Re: Assembly and meta stuff released ??
Message-ID: <1045588514.3e526a22a550c@www.nexenservices.com>
Date: Tue, 18 Feb 2003 18:15:14 +0100 (CET)
From: dvillevalois@phpapp.org
References: <1045578534.3e52432663b3f@www.nexenservices.com>
 <3E5250A1.2060006@apache.org>
 <1045583356.3e5255fc7e4ad@www.nexenservices.com>
 <b2tm0g$86f$1@main.gmane.org>
In-Reply-To: <b2tm0g$86f$1@main.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP IMAP webmail program 2.2.6

> It has not been determined at all how much of
> this code will come from the current merlin and assembly dirs in 
> sandbox. I'm kinda wondering here how all you guys got this idea...?

Digging in all the containers, you can quickly see common concepts and
mechanisms... This makes obvious to me that the goal there was to converge.

> your question is unclear...what do you mean by framework? We always 
> distinguish avalon-framework (the stuff in the "avalon" cvs module) from
> everything else. Avalon-framework is complete, and its component package
> has been deprecated for a year or so (ever since 4.1 I think).

Okay, i'll dig it better.

> > I could help a lot on documentation as a start...

Last question : Do you know a diff for windows that has the same output as diff ??

Thanks. A+. Didier Villevalois.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org