Hi Paul, Re your questions on the branching set up for V3 docs.
I'm not a CVS expert by any means, so if I'm being stupid in what follows, just laugh and ignore me! ;-) Is it possible to set up a branch under the trunk and another under the same position in the B_Release? Or is that not possible. When I'm finished doing a document, I commit it in trunk, then copy it wholesale to my local B_Release and commit it from there - after a test build. I am, now, wondering if this is a good idea. What about the other languages for translations, would they be branched as well? What about build.sh, would that need looking at too? I'm thinking I might be creating a lot of work - for other people - for what now appears to be minimal returns. So, on second thoughts, I propose we leave everything as it is and when I get around to creating a new document for, say, V3 gsec, then I shall call it fbutil_gsec_v3.xml and when I add it to the web site for download, assuming I can still do that, we could simply add a new V3 section there for the docs? Am I making sense? Cheers, Norm. -- Norman Dunbar Dunbar IT Consultants Ltd Registered address: 27a Lidget Hill Pudsey West Yorkshire United Kingdom LS28 7LG Company Number: 05132767 ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
