kgio RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Aaron Patterson <tenderlove@ruby-lang.org>
To: Ngan Pham <nganpham@gmail.com>
Cc: Eric Wong <e@80x24.org>, kgio-public@yhbt.net
Subject: Re: Patch for GC.compact memory issue
Date: Tue, 25 May 2021 09:41:09 -0700	[thread overview]
Message-ID: <CAPJJa7txP7D9s5AOLFxs_Kxuvq_Yx_5BBYMbafdn8LaGjb-yvA@mail.gmail.com> (raw)
In-Reply-To: <CAAvYYt6ruhhZcA4OmF=NQZ+-j0RJ0vT5f33tUCrREezo5mUCVQ@mail.gmail.com>

On Mon, May 24, 2021 at 2:11 PM Ngan Pham <nganpham@gmail.com> wrote:
>
> > Side note: Sorry if you found it confusing, I figured "README"
> >   and "HACKING" are clearly labeled.  Not sure how to improve on
> >   a directory listing for ease-of-navigation (works with "lftp" :>)
>
> My apologies! After actually spending time and reading your
> docs, it's pretty straight forward. Perhaps I'm spoiled with GitHub
> pull requests and whatnot. The HACKING doc also says "pull
> requests" welcome, although I'm not sure where...
>
> > OK, so rb_const_get for things like Socket, Errno::EPIPE,
> > Errno::ECONNRESET are fine (for now)?
>
> I'll defer to Aaron. :-)


Yes, they should be fine.  It looks like they're all defined with
`rb_define_const`, and that function adds them to a list that gets
pinned.

  parent reply	other threads:[~2021-05-25 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 14:14 Patch for GC.compact memory issue Ngan Pham
2021-05-24 17:22 ` Eric Wong
2021-05-24 19:00   ` Ngan Pham
2021-05-24 20:33     ` Eric Wong
2021-05-24 21:11       ` Ngan Pham
2021-05-24 21:48         ` [PATCH] HACKING: update docs with "git request-pull" info Eric Wong
2021-05-25 16:41         ` Aaron Patterson [this message]
2021-05-25 22:50           ` Patch for GC.compact memory issue Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/kgio/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPJJa7txP7D9s5AOLFxs_Kxuvq_Yx_5BBYMbafdn8LaGjb-yvA@mail.gmail.com \
    --to=tenderlove@ruby-lang.org \
    --cc=e@80x24.org \
    --cc=kgio-public@yhbt.net \
    --cc=nganpham@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/kgio.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).