From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] ruby: bump to version 2.1.2
Date: Fri, 29 Aug 2014 09:56:01 +0200 [thread overview]
Message-ID: <87ppfjrapa.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20140829091725.1fd32d4d@free-electrons.com> (Thomas Petazzoni's message of "Fri, 29 Aug 2014 09:17:25 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> I don't really know much about Ruby. Is 2.1.x compatible with 1.9.x or
>> is it like Python2/Python3?
> I don't really know much about Ruby either. But, about Ruby 2.0,
> Wikipedia says:
> ""
> Ruby 2.0 is intended to be fully backward compatible with Ruby 1.9.3.
> As of the official 2.0.0 release on February 24, 2013, there were only
> five known (minor) incompatibilities.
> ""
> And then, about Ruby 2.1, they say:
> ""
> Ruby 2.1.0 was released on Christmas Day in 2013.[31] The release
> includes speed-ups, bugfixes, and library updates. Starting with 2.1.0,
> Ruby is using semantic versioning.
> ""
> So I believe we can simply bump the ruby package to 2.1, and not bother
> keeping two separate packages.
Ok, thanks - Committed to next.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2014-08-29 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 22:17 [Buildroot] [PATCH 0/3] Misc Ruby updates Thomas Petazzoni
2014-08-28 22:17 ` [Buildroot] [PATCH 1/3] ruby: requires shared library Thomas Petazzoni
2014-08-29 7:16 ` Peter Korsgaard
2014-08-28 22:17 ` [Buildroot] [PATCH 2/3] ruby: should not use dl_iterate_phdr() on Blackfin Thomas Petazzoni
2014-08-29 7:16 ` Peter Korsgaard
2014-08-28 22:17 ` [Buildroot] [PATCH 3/3] ruby: bump to version 2.1.2 Thomas Petazzoni
2014-08-29 7:15 ` Peter Korsgaard
2014-08-29 7:17 ` Thomas Petazzoni
2014-08-29 7:56 ` Peter Korsgaard [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ppfjrapa.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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