Re: [Flightgear-devel] Developers
On Fri, May 21, 2010 at 3:32 AM, Peter Morgan p...@freeflightsim.orgwrote: 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! I encourage people to submit patches either to the mailing list -- using git format-patch -- or through the merge request process on gitorious. By the way, I merged two of Anders' merge requests today. I did this because they seem to be well isolated and I trust Anders not to screw things up, but in general I will not be handling merge requests in fgdata because I'm simply not qualified to vet random changes to aircraft. I encourage people who have commit rights to fgdata to review merge requests and merge them; I'll be happy to help with the git mechanics. Tim -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Developers
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. -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Developers
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
Re: [Flightgear-devel] Developers
Peter Morgan wrote: 2) two patches have already been submitted to this list and NONE have been appliced As far as my memory serves (I might be wrong and I'm currently not in a position to check) someone's been posting plausible objections against at least one patch for the B787 which (the objections) had never been adressed. Therefore the patch has not been applied so far. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Developers
Martin Spott wrote: As far as my memory serves (I might be wrong and I'm currently not in a position to check) someone's been posting plausible objections against at least one patch for the B787 which (the objections) had never been adressed. Yup, here's the respective posting: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg25828.html As far as I understand this means: The patch doesn't contain the proper fix. Therefore I've refrained from committing to CVS (now: GIT). Looks like the patch needs a patch ;-) Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Developers
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 -- ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
