kgio RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <>
To: Ngan Pham <>
Subject: [PATCH] HACKING: update docs with "git request-pull" info
Date: Mon, 24 May 2021 21:48:44 +0000	[thread overview]
Message-ID: <20210524214844.GA27131@dcvr> (raw)
In-Reply-To: <>

Ngan Pham <> wrote:
> Eric Wong 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...

No worries, thanks for the feedback; I guess "git request-pull"
is not well-known.  I don't care where people host their repos,
as long as it's anonymously accessible from any country via
"git fetch".

Subject: [PATCH] HACKING: update docs with "git request-pull" info

"git request-pull" is not a well-known command, so add a
mention about it to avoid misleading people into thinking
we use a centralized service.

While we're in the area, put an extra link to the HTTPS
archives, since SMTP-based subscriptions are not

Thanks to Ngan Pham for the feedback.

 HACKING | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/HACKING b/HACKING
index e124c33..55bdd99 100644
@@ -23,11 +23,12 @@ characters wide) and NOT the indentation style of Matz Ruby.
 == Contributing
-Contributions are welcome in the form of patches, pull requests, code
-review, testing, documentation, user support or any other feedback.  The
-{kgio mailing list}[] is the
-central coordination point for all user and developer feedback and bug
+Contributions are welcome in the form of patches, pull requests
+(format email with "git request-pull"), code review, testing,
+documentation, user support or any other feedback.
+<> <> is the
+current coordination point for all user and developer feedback and
+bug reports (domain is subject to change since ICANN cannot be trusted).
 === Submitting Patches

  reply	other threads:[~2021-05-24 21:48 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         ` Eric Wong [this message]
2021-05-25 16:41         ` Aaron Patterson
2021-05-25 22:50           ` 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:

  List information:

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

  git send-email \
    --in-reply-to=20210524214844.GA27131@dcvr \ \ \ \

* 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

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).