On Sat, 22 Jan 2011, Ruediger Pluem wrote:
How to handle?[ ] 1. change the 2.2 doc to reflect the actual 2.2 behavior [ ] 2. backport the trunk behavior as-is, so 2.0/2.2/trunk behave the same [ ] 3. backport the trunk behavior, but using a new option to avoid breaking existing configurations that might depend on the current behavior[X] 4. backport the trunk behavior, but using a new option to set the current 2.2 behavior to avoid breaking existing configurations from 2.0/trunk but enable 2.2 users that rely on the new 2.2 behavior to get this back
+1. AIUI, this is the same as on/off/decode in Bill's proposal.
