[Flex-devel] posting patches

[Will E. <wl...@us...>]

All,

It recently came to my attention that I wasn't subscribed to the
flex-devel mailing list. As maintainer, it's definitely a good thing
that I be in touch with folks who are interested in the guts of the flex
program.

There was a question posted back in May regarding how best to propose
patches for inclusion in flex.

In general there's not a simple answer, but there are some basic
guidelines that it'd be helpful to keep in mind:

* Shorter patches are easy to evaluate.

* Too many patches in too short a time can flood my capacity to evaluate
  them.

* If you have a set of related patches, keep them together.

* If you're proposing some big overriding change to flex, talk about it
  on flex-devel first.

As for the particular documentation patch in question, I just
incorporated (most of) it into the flex cvs tree.

So, thanks, Dustin for submitting the patch.

--Will