[#81492] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — normalperson@...
Issue #13618 has been reported by normalperson (Eric Wong).
12 messages
2017/06/01
[#88695] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/08/27
> https://bugs.ruby-lang.org/issues/13618
[#81569] [Ruby trunk Feature#12589] VM performance improvement proposal — vmakarov@...
Issue #12589 has been updated by vmakarov (Vladimir Makarov).
3 messages
2017/06/04
[#81581] [Ruby trunk Bug#13632] Not processable interrupt queue for a thread after it's notified that FD is closed in some other thread. — sir.nickolas@...
Issue #13632 has been reported by nvashchenko (Nikolay Vashchenko).
4 messages
2017/06/05
[#81590] Re: [ruby-cvs:66197] ko1:r59023 (trunk): revert r59020 because it may fail some tests sometimes on some environment (http://ci.rvm.jp/). This revert is to check the reason of failures. — Eric Wong <normalperson@...>
ko1@ruby-lang.org wrote:
5 messages
2017/06/06
[#81591] Re: [ruby-cvs:66197] ko1:r59023 (trunk): revert r59020 because it may fail some tests sometimes on some environment (http://ci.rvm.jp/). This revert is to check the reason of failures.
— Eric Wong <normalperson@...>
2017/06/06
Eric Wong <normalperson@yhbt.net> wrote:
[#81596] Re: [ruby-cvs:66203] Re: Re: ko1:r59023 (trunk): revert r59020 because it may fail some tests sometimes on some environment (http://ci.rvm.jp/). This revert is to check the reason of failures.
— Eric Wong <normalperson@...>
2017/06/06
Eric Wong <normalperson@yhbt.net> wrote:
[#81825] [Ruby trunk Feature#13697] [PATCH]: futex based thread primitives — normalperson@...
Issue #13697 has been reported by normalperson (Eric Wong).
3 messages
2017/06/29
[ruby-core:81766] Re: [Ruby trunk Feature#10771] An easy way to get the source location of a constant
From:
Eric Wong <normalperson@...>
Date:
2017-06-25 09:59:33 UTC
List:
ruby-core #81766
jeremy.phelps@instacart.com wrote: > I've got a patch ready for this, but I have no idea how to > submit it. There are serious contradictions in this page: > > https://bugs.ruby-lang.org/projects/ruby/wiki/HowToContribute > > It says that the changes should be against "the trunk of > Ruby", and that "only Ruby 2.4 may accept new features." But > the trunk on GitHub is Ruby 2.5. Make the change against trunk, any mentions of specific version numbers is probably outdated. Maybe you have permissions to edit that page? (I can't stand <form> inputs in web browsers and reply to redmine via email) > It says that the patch should be a unified diff, but it also > says different changes should not be mixed in a single commit. > But diff files don't have commits; only pull requests and > whole repos do. But it says that you only accept PRs for "tiny > fixes", and only if they don't require discussion. The output of "git format-patch" is a superset of unified diff, you should use that to generate diffs if using git. "git am" can be used to apply that output and preserve authorship info and the commit message. You can also publish your work to any publically accessible git repository tell us about how to pull it, here. The "git request-pull" command can generate the message text for you. Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>