Issue #12421 has been updated by Usaku NAKAMURA.


+ About 2.0.0, we will never backport any patches because it has already reached at end-of-life.
+ About 2.1, it has no chance to backport any features because it's in security only maintenance phase.
+ About 2.2, in principle, feature changes are not backported.  If someone persuade us (especially, me) to understand that this is a spec bug, I'll backport it.
+ About 2.3, same as 2.2.

----------------------------------------
Bug #12421: Please backport r53816, r53817
https://bugs.ruby-lang.org/issues/12421#change-59856

* Author: Vit Ondruch
* Status: Open
* Priority: Normal
* Assignee: 
* ruby -v: ruby 2.0.0p598 (2014-11-13) [x86_64-linux]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
Since there was request to fix this issue on RHEL7 [1], which ships Ruby 2.0.0 and the fix was applied just to trunk, I expect that all other supported Ruby versions suffer this issue as well as Ruby 2.0, therefore it would be nice to have this backported (although this might be considered feature, not a bug).

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1300433



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>