On 27/10/11 11:30, David wrote: >> On 27/10/11 10:10, David wrote: >>>> Should I create a new branch and do the updates to it, try to do >>>> incrementally, because some of the files change a few times for different >>>> things. Do I have access to branch? >>> Looks like the way to go - but I have to wait until I have permission. >>> >> I don't quite understand the question -- are you asking for SVN write >> access, or something entirely different? You can create a 'local' >> repository (on your own machine) and initialise it with the current fltk >> svn version. You can then quite easily branch this and apply updates / >> etc as you see fit, and then 'svn diff' your branch against the current >> head (which you continually 'svn up' against 1.3) >> >> Ben >> > Yes write, to create a branch so you guys can see the incremental updates > easily (I presume svn keeps a history that can be used to see various > versions). If I just did diff's you'd only see the changes combined with the > other changes. >
See, the difference between git and SVN is that write access actually gives you write access to the *whole* repository, rather than just the ability to create your own repo that the developers can rebase from. With this in mine, though I'm in no way speaking officially (as I don't really do any of the 1.3 dev work) the chances that you'll get write access granted so you can run a parallel repo is extremely slim, as in effect this means you're able to write to 1.3 just as Matthais / Albrecht / any of the core developer team are. What might be more viable is having your own changes on your machine and when you're happy with the final state of these, submit a unified diff. This way the developers can pour over it when it's done and work out whether or not to make it part of "official" FLTK. IIRC this is what is done with the Gleam scheme, so it's not entirely a concept the developers are adverse to - though it's probably worth waiting for one of the 1.3 guys to confirm here. Ben _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
