1 Patch guidelines

This section lists some guidelines for writing a good patch which is
more likely to be accepted.

Any new features or large scale work should first be discussed on the
evolution-hackers list first.  This will ensure the idea fits in the
direction we wish to take Evolution, and also that the effort is not
duplicated.  See section 3 for details on the mailing lists.

1.1 Patch basics

o The patch should apply cleanly at the time it is made.

o It must compile once applied.

o It must not generate any more compile time warnings than were
  already there.  This may be platform dependent so simply do your
  best.

o It must conform to C89/C90 (ANSI/ISO C), and build with gcc using
  the default compile flags.

  The primary trap is that in C99 you may define variables anywhere in
  the code, in C89 they must be declared in a declaration block which
  follows any block start '{'.

  If you wish to ensure the code is C89, try the following.

  From the gcc manual page:
                                                           "To select
  this standard in GCC, use one of the options `-ansi', `-std=c89' or