On Fri, May 21, 2010 at 1:19 PM, Reagan Thomas <thomas...@gmail.com> wrote:
> Peter Morgan wrote: > > Its is/was bit of a "dark" how to get commit "permission" to FG and > > its seems to be one Curt in control. > > > > Can someone explain to process to submitting patches to this new git > > scenario, or are we to be held in the grey area of hopefulnes as well ? > > > > eg I'd like to submit a patch for the 787 that actually makes it boot up! > > > > pete > > ------------------------------------------------------------------------ > > > > > ------------------------------------------------------------------------------ > > > > > As always, you can submit your patch on this list, along with a clear > description of what problem it is solving and how it solves it. That > serves as notification to the original aircraft developer (Josh Wilson > in this case) and gives others on the list a chance to see the changes > in case Josh is on walk-about. If he doesn't respond and folks on the > list agree to patch is cool, I'm sure someone will commit it. > > 1) ave tried to contract Josh for a long time but is missing 2) two patches have already been submitted to this list and NONE have been appliced 3) Developers do not want to "mess" with an aircraft designers repos.. 4) Catch 22 Imho we might as well remove 787 from the Repos, its broken, unmaintained, and just taking up space, as well as frustrating other users who might want to try. pete > > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel >
------------------------------------------------------------------------------
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
