How are patches organized?
Prior to version 4.0 I posted patches to the ncurses mailing list summarizing only my changes (after applying changes submitted by others). The intent was that people who followed the list closely could build developmental versions. Generally (unless we find a serious error), I issue patches on Saturdays, since validating patches takes time. Beginning with version 4.0, I maintain “complete” patches (my changes together with those that I have integrated). It is simpler, and does not require making complete snapshots as often. • User-supplied patches that require no modification are always tagged with their name, making it simpler to follow the revision history. • User-supplied patches that require some modification are still tagged, but my patch will have followup changes. Most files have RCS identifiers. If you are maintaining ncurses in an RCS (or CVS, etc.
Prior to version 4.0 I posted patches to the ncurses mailing list summarizing only my changes (after applying changes submitted by others). The intent was that people who followed the list closely could build developmental versions. Generally (unless we find a serious error), I issue patches on Saturdays, since validating patches takes time. Beginning with version 4.0, I maintain “complete” patches (my changes together with those that I have integrated). It is simpler, and does not require making complete snapshots as often. • User-supplied patches that require no modification are always tagged with their name, making it simpler to follow the revision history. • User-supplied patches that require some modification are still tagged, but my patch will have followup changes. Most files have RCS identifiers.
