Hi Justin, You only need a local working-copy of official apache/flex and GitHub owner access over it, later apply the pull-request commit in you local copy into a topic branch for this issue, if all works fine, accept the pull-request in GitHub, and update de official develop branch from there into your local develop branch, later merge or move the change over svn-integration branch and later use svn from console or whatever be your favourite svn tool for make commit against the official repo.
In the other hand, you and others like you, may have an own fork and admit pull-request over it, and later follow the same process, but the first way feels better.. J. On Aug 17, 2012, at 11:22 PM, Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > Again no path file which means I have to generate one myself. Worse case it > seems that git patch files are not compatible with SVN patch file so I'm > still unable to apply the patch. I could hand create or re do the changes in > SVN but that's going to get tedious fast for anything but trivial changes. > > I managed to find this and may try out a few things it suggests later today: > http://stackoverflow.com/questions/708202/git-format-patch-to-be-svn-compatible > > Justin
