Quoting Andrew Midosn:
> --- Frederic Bouvier <[EMAIL PROTECTED]> wrote:
> > Thanks for your efforts. I just have practical
> > remarks regarding patch post to
> > the list.
> > Use unidiff ( -u ) because all those > are confusing
> > mail readers that interpret
> > added lines as message quote
> > Attach the file because many lines are split
> > Better yet, send directly to one maintainer with CVS
> > write access
> > This way you will avoid the frustration of having
> > your patch ignored just
> > because it is unusable without a man-month worth of
> > effort to rebuild something
> > that could be understood by the patch utility.
> Thanks for the advice. I'll try and sort that out when
> I get back from work. Who would be the best person to
> send the diffs to?
It depends of the patch. Curt and Erik have full access ( with DavidM but he is
offline for several weeks ). Some specific modules have their own maintainer
with write access restricted to the directory they manage ( Andy for yasim,
DaveL for ATC, Jim can access the base package ). You can have a look at
flightgear-cvslog for a track of who is doing what.
Flightgear-devel mailing list