On Fri, May 21, 2010 at 3:32 AM, 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
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:/
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 obj
On Fri, May 21, 2010 at 1:19 PM, Reagan Thomas 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 h
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 su
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 actu
6 matches
Mail list logo
