On Fri, June 30, 2006 11:54 am, Bruno Postle said:
>> I have branched all the modules in panotools:
>> drwxrwxr-x 8 dmg dmg 4.0K Jun 30 07:49 clens/
>> drwxrwxr-x 3 dmg dmg 4.0K Jun 30 07:49 CVSROOT/
>> drwxrwxr-x 3 dmg dmg 4.0K Jun 30 07:50 gimp-plugin/
>> drwxrwxr-x 6 dmg dmg 4.0K Jun 30 07:50 gimp-plugin-ng/
>> drwxrwxr-x 8 dmg dmg 4.0K Jun 30 07:50 libpano/
>> drwxrwxr-x 6 dmg dmg 4.0K Jun 30 07:49 Panotools-Script/
>> drwxrwxr-x 7 dmg dmg 4.0K Jun 30 07:50 ptfilter/
>> Perhaps we might want to delete some (like CVSROOT) or all except
>> libpano. I guess at this point it does not harm to keep them all.
My old attempt at making PTStitcher should be removed. Daniel's PTMender is the way of
I would like to put the various tools into seperate folders.
> There is no need to branch for any except libpano. Also do we want
> to move all the 'panotools' projects to subversion? or just libpano?
The change in the structure will likely effect clens, plugin, and ptfilter. I think we
need to keep everything branched. Not looking at the code to be sure.
> Does anyone need help with this switch from CVS to subversion? I
> guess it might be confusing if you are not familiar with all this
I think the hardest part of setting my computer back up with a development enviroment
was getting the CVS working correctly. I use subversion a little bit at work already so
I hope this wont be an issue for me.
>> Bruno, is there a way to "close" write access to the CVS repository?
> Yes, each developer can have their CVS access withrawn, so we can do
> this if we are moving everything to subversion permanently.
I think everything has been moved.
Yahoo ID: j1vvy ymsgr:sendIM?j1vvy
jwatters @ photocreations . ca