From: Eric Wong <normalperson@yhbt.net>
To: ruby.io.splice@librelist.org
Subject: [PATCH 2/2] .gitignore: add .rbx
Date: Sun, 12 May 2013 20:02:56 +0000 [thread overview]
Message-ID: <1368388976-20489-2-git-send-email-normalperson@yhbt.net> (raw)
In-Reply-To: 1368388976-20489-1-git-send-email-normalperson@yhbt.net
Newer versions of Rubinius generate files in .rbx.
---
.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/.gitignore b/.gitignore
index 8054019..12e180f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,6 +2,7 @@
*.so
*.log
*.rbc
+.rbx
Makefile
/GIT-VERSION-FILE
/local.mk
--
1.8.2.1.367.gc875ca7
prev parent reply other threads:[~2013-05-12 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 20:02 [PATCH 1/2] io/splice: deprecated potentially unsafe methods Eric Wong
2013-05-12 20:02 ` Eric Wong [this message]
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/ruby_io_splice/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1368388976-20489-2-git-send-email-normalperson@yhbt.net \
--to=normalperson@yhbt.net \
--cc=ruby.io.splice@librelist.org \
/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/ruby_io_splice.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).