John,
I am not sure if this helps at all but I had to do a very similar exercise with the SuSE port.  Brian W. helped me considerably during the process.  Only problem I see is that in the case of the SuSE port it was almost entirely based on Fedora 3 OpenSSI.  I believe this was partly done as the distros are pretty similiar ( use rpms etc.).  From the few times I have installed the Debian version of OpenSSI I noticed there are a lot more differences.  The question I would ask is: was the Debian port at some point based on Fedora 3 OpenSSI?  

-Karl

On 12/20/06, John Hughes <john@calva.com> wrote:
John Hughes wrote:
In http://wiki.openssi.org/go/CVS_Administration it says:

NOTE: Should discuss how branches are synchronized using the MERGE-* tags.

Could someone give me some hints about what exactly is meant by this?
If it means I should do

    cvs up -jMERGE-DB-FC -jOPENSSI-FC

then it's pretty much a non-starter as it seems some vendor FC updates have been merged in.

NOTE: Emphasize that before merging a branch with newer base code, all recent OpenSSI/CI changes to that branch should first be synced to all other branches. Otherwise, the recent OpenSSI/CI changes are lost in the "noise" of the base changes.

And this?
As I said OPENSSI-FC seems to have some base code merges and the debian merge tags haven't been updated.

I'd guess that I just have to move the debian tags - no merge is needed.  True?


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
ssic-linux-devel mailing list
ssic-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel