From: v.ondruch@tiscali.cz
To: ruby-core@ruby-lang.org
Subject: [ruby-core:84267] [Ruby trunk Feature#5313] Please drop IRB's version in favour of Ruby version
Date: Thu, 14 Dec 2017 14:04:57 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-68422.20171214140455.d9450d4933ce968d@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-5313.20110913160930@ruby-lang.org
Issue #5313 has been updated by vo.x (Vit Ondruch).
This is still issue. Gemifying IRB might help with that ...
----------------------------------------
Feature #5313: Please drop IRB's version in favour of Ruby version
https://bugs.ruby-lang.org/issues/5313#change-68422
* Author: vo.x (Vit Ondruch)
* Status: Assigned
* Priority: Normal
* Assignee: keiju (Keiju Ishitsuka)
* Target version: next minor
----------------------------------------
It seems that IRB's upstream lives in Ruby's SVN. There is no way how to update IRB separate from Ruby. From that point of view, it would make sense to drop IRB's own version numbers in favour of Ruby versions instead. The IRB reports this version information:
> irb -v
irb 0.9.6(09/06/30)
However from the IRB changelog [1] it is clear that there went some changes in meantime, so the IRB's versioning is not reliable and does not make a sense IMO.
[1] https://github.com/ruby/ruby/commits/trunk/lib/irb
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2017-12-14 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 7:09 [ruby-core:39505] [Ruby 1.9 - Feature #5313][Open] Please drop IRB's version in favour of Ruby version Vit Ondruch
2011-09-13 9:03 ` [ruby-core:39507] [Ruby 1.9 - Feature #5313][Assigned] " Nobuyoshi Nakada
2012-11-20 11:54 ` [ruby-core:49680] [ruby-trunk - Feature #5313] " mame (Yusuke Endoh)
2017-12-14 14:04 ` v.ondruch [this message]
2018-04-19 7:52 ` [ruby-core:86600] [Ruby trunk Feature#5313] " hsbt
2018-11-27 8:53 ` [ruby-core:90088] [Ruby trunk Feature#5313][Closed] " v.ondruch
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-68422.20171214140455.d9450d4933ce968d@ruby-lang.org \
--to=ruby-core@ruby-lang.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.
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).