Sylvain Beucler <[EMAIL PROTECTED]> tapota : > Hi, > > After upgrading to Savane a while ago, we had to reinsert a lot of > custom changes made at Savannah by various people. >
backend only? > > In order to perform seamless upgrades when new versions of Savane >are released, we are willing to either: - integrate our changes in >Savane, - provide a mean to externalize code that is too much >site-specific (eg, providing a way to add local functions like >CvsMakeArea in the backend via hooks, as documented in a sv_group's >FIXME) > > Creating a branch would be better to do the job. > > Is it ok, and is there any precautions we should take, given that > another branch is being actively worked on? It may create cvs conflicts, depending on how big are the changes needed. For stuff like CvsMakeArea, I think easier, in a first time, to add directly your own subs within the module, like I did for Gna! ones. At a later point (after the release; so after the merge of the dev branch into the trunk), it will more easy to externalize site-specific code. What do you think? -- Mathieu Roy +---------------------------------------------------------------------+ | General Homepage: http://yeupou.coleumes.org/ | | Computing Homepage: http://alberich.coleumes.org/ | | Not a native english speaker: | | http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english | +---------------------------------------------------------------------+
