Hi Rüdiger,
Rüdiger Timm wrote:
Hi Giuseppe,
Giuseppe Castagno wrote:
Hi all,
<snip>
The steps I intend to follow are:
1. Finishing committing in HEAD all the new module files (see [4] for
a module description), through the alias.
2. On the new cws I'm going to create, I'll add only the OOo module that
needs to be adapted (vcl) and made it dependent to the new one.
3. I'll then add a note on EIS about the new module to be added while
integrating.
4. Go on with the usual work, committing vcl changes to CWS and the new
module changes to HEAD.
My questions are:
- are these steps the correct ones?
Yes, that's correct.
- is there a way to have the new CWS built on buildbot?
Unfortunately not.
- the new module (icc, [4], in external/icc) should be added to the CWS
or should I continue to commit the code in that module alone to HEAD?
New modules not yet in the master workspace cannot be added to a CWS.
You have to continue working head.
thanks Rüdiger, I'll proceed as you suggested.
--
Kind Regards,
Giuseppe Castagno
Acca Esse http://www.acca-esse.eu
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
