21819-23811

21632-25255 subjects 22013-22844

Re: [redmine4ruby-lang:236] [Bug #1099] Invalid value of StringIO#pos after StringIO#ungetc
21819 [yugui@yu ui ] The following issue was reported to the redmine4ruby-lang project but it

[Bug #1100](Closed) parsing bad YAML crashes interpreter
21820 [redmine@ru y] Issue #1100 has been updated by Yukihiro Matsumoto.

[Feature #1102] Prepend Module
21822 [redmine@ru y] Feature #1102: Prepend Module
21922 [rogerdpack@g] I suppose one [not too useful] hack at it could be something like
22971 [transfire@gm] he class hierarchy (ie. > the method lookup order). This of course makes se=

[Bug #1103] Ruby used for webrick cgi should be configurable
21823 [redmine@ru y] Bug #1103: Ruby used for webrick cgi should be configurable

[Bug #1098](Rejected) Unclear encoding error: #<Encoding::UndefinedConversionError: "\xE2\x96\x80" from UTF-8 to ISO-8859-1 in conversion from CP850 to ISO-8859-1>
21827 [redmine@ru y] Issue #1098 has been updated by Yui NARUSE.

Re: [Bug #1098](Rejected) Unclear encoding error: 
21829 [micathom@gm ] It wasn't there in the original script. But you're right.

[Feature #1106] Script encoding vs. default_internal: Implicitly transcode strings/regexps
21830 [redmine@ru y] Feature #1106: Script encoding vs. default_internal: Implicitly transcode strings/regexps

[Feature #1106] Script encoding vs. default_internal: Implicitly transcode strings/regexps
21832 [redmine@ru y] Issue #1106 has been updated by Yui NARUSE.

[Bug #1108] Typo in String#codepoints documentation.
21835 [redmine@ru y] Bug #1108: Typo in String#codepoints documentation.

What does this regexp mean - /\c#{_J}/
21838 [Shri.Borde@m] I am combining the escaped control character syntax (\cX) with variable int=
21839 [charles.nutt] No warnings in JRuby but we appear to do the same thing. Parser artifact
+ 21841 [Shri.Borde@m] Makes sense
+ 21848 [nobu@ru y- a] Not a bug.  The regexp is same as /a{_J}/, which lacks numeric range
+ 21860 [Shri.Borde@m] Actually, with strings, the regexp is evaluated at the very end after substituting all the variables. So this should have actually worked. Here is the spec I will add. The not_compliant_on(:ruby) means that it is a Ruby bug
  21867 [Tomas.Matous] \c converts the following character (which happens to be # in this case) to a control character. So #{} is not treated as an expression in this case.
  + 21869 [Shri.Borde@m] Ah, ok.
  + 21874 [murphy@ru yc] thank you both, I was able to fix a related bug in my highlighting

[Feature #1106] Script encoding vs. default_internal: Implicitly transcode strings/regexps
21840 [redmine@ru y] Issue #1106 has been updated by Michael Selig.

Regexp interpolation does not give equality
21842 [Shri.Borde@m] Any idea why the second expression results in false? Its seems like both th=
21851 [neleai@se na] irb(main):001:0> a="a"
21861 [Shri.Borde@m] Yes, I realized this later. Substitution always uses to_s, and to_s of a Re=
21868 [murphy@ru yc] funny topic :) deciding whether two given regular expressions represent

1.9.1 'official' tag
21843 [dave@pr gp o] What's the official svn tag for the 1.9.1 release? I see tags for
21916 [rogerdpack@g] ruby 1.9.1p0 (2009-01-30 revision 21907) [i386-mswin32_90]

[Bug #448](Rejected) URI::join does not concatenate all strings passed in
21845 [redmine@ru y] Issue #448 has been updated by akira yamada.

[Bug #454](Rejected) URI does not follow the last rfc about uri syntax
21846 [redmine@ru y] Issue #454 has been updated by akira yamada.

[Feature #1013](Rejected) Handling of [ and ] in URIs
21847 [redmine@ru y] Issue #1013 has been updated by akira yamada.

[Bug #738] Repeated calls to popen cause thread problems
21849 [redmine@ru y] Issue #738 has been updated by Michal Suchanek.

[Feature #1106] Script encoding vs. default_internal: Implicitly transcode strings/regexps
21852 [redmine@ru y] Issue #1106 has been updated by Tom Link.

[Bug #1113] Compilation fails on Ubuntu 8.10, 64 bit
21855 [redmine@ru y] Bug #1113: Compilation fails on Ubuntu 8.10, 64 bit
21857 [shiba@ma l2 ] I got the same situation with GCC 4.3.2. (on Debian lenny)
21875 [nobu@ru y- a] Or optflags=-O3 prevents it, and defaulted in trunk.

[Bug #883] Failure: test_handle_special_CROSSREF_no_underscore(TestRDocMarkupToHtmlCrossref)
21858 [redmine@ru y] Issue #883 has been updated by Kazuhiro NISHIYAMA.

[Bug #1108](Closed) Typo in String#codepoints documentation.
21862 [redmine@ru y] Issue #1108 has been updated by Yukihiro Matsumoto.

Bug with [:lower:]
21863 [Shri.Borde@m] [:upper:] works as expected. [:lower:] matches incorrectly to an empty posi=
21865 [matz@ru y- a] It's not a bug.  You've specified ZERO or more lower case letters, so
21866 [Shri.Borde@m] Yes, my mistake.

[Bug #1116] Compilation error for Solaris 10 sparc
21870 [redmine@ru y] Bug #1116: Compilation error for Solaris 10 sparc
21872 [akr@fs j. rg] The return statement is introduced by r20877 by yugui.

Redmine gateway (was Re: [Bug #1113] Compilation fails on Ubuntu 8.10, 64 bit)
21871 [dooby@d1 .k ] Can someone, please, clarify whether the Redmine gateway should be

[FEATURE:trunk] Fw:adding support for linux SO_ATTACH_FILTER socket option
21873 [yugui@yu ui ] The following issue was reported to the redmine4ruby-lang project but it
21876 [akr@fs j. rg] Why it cannot be dealt with Socket#setsockopt?

[Bug #1066] Frequent failure: test_io.rb test 2 on OS X 10.5.6
21877 [redmine@ru y] Issue #1066 has been updated by Akira Tanaka.

[Bug #1093] make test fails
21878 [redmine@ru y] Issue #1093 has been updated by Akira Tanaka.

[Bug #1113](Third Party's Issue) Compilation fails on Ubuntu 8.10, 64 bit
21879 [redmine@ru y] Issue #1113 has been updated by Shyouhei Urabe.

[Bug #1117] Array#choice always produces the same sequence
21880 [redmine@ru y] Bug #1117: Array#choice always produces the same sequence
21882 [murphy@ru yc] actually, why isn't srand initialized with Time.now.to_i or just 0 by
21883 [matz@ru y- a] Don't worry, it is now.  Those two problems were fixed at the same
21885 [murphy@ru yc] I'm sorry :)

[Bug #1117](Closed) Array#choice always produces the same sequence
21881 [redmine@ru y] Issue #1117 has been updated by Shyouhei Urabe.

[Bug #1118] irb core dumps with 'CTRL-C' with zsh
21884 [redmine@ru y] Bug #1118: irb core dumps with 'CTRL-C' with zsh

mule-utf-8
21886 [romanbsd@ya ] unknown encoding name: mule-utf-8
21892 [naruse@ai em] You know ruby can't support all the encodings in the world.
21895 [romanbsd@ya ] I'm also not familiar with this encoding, I was surprised as well.
+ 21896 [naruse@ai em] Thanks
+ 21927 [duerst@it ao] I think for the reported issue, the best thing is to fix

[Bug #1113] Compilation fails on Ubuntu 8.10, 64 bit
21887 [redmine@ru y] Issue #1113 has been updated by Rados??aw Bu??at.

[Bug #1120] [PATCH] fix build on GNU/kOpenSolaris
21888 [redmine@ru y] Bug #1120: [PATCH] fix build on GNU/kOpenSolaris

[Feature #1122] request for: Object#try
21893 [redmine@ru y] Feature #1122: request for: Object#try
+ 21898 [murphy@ru yc] I mostly use @person.name rescue nil ^_^ #try is nice.
+ 21907 [mame@ts .n .] Interesting.  I think `try' is good enough for me as non-native.
  21909 [dblack@ru yp] I don't think that's a big issue, because you'd probably either use
  + 21923 [mame@ts .n .] I don't expect that we will do it *back and forth*, but I think
  | + 21924 [hramrach@ce ] That looks pretty good except it would need parser changes, and would
  | + 21932 [dblack@ru yp] I think in most cases you'd know whether you're going to do this
  |   21968 [calcifer@ru ] You could slightly modify it to be
  |   21972 [dblack@ru yp] Sorry but that's syntactic vinegar :-)
  |   21973 [radek.bulat@] Providing new syntax change for such a small thing is IMHO
  |   22165 [wycats@gm il] Count me in as a +1 on foo.?bar(baz). I'm on the fence about whether ?bar
  |   + 22177 [dev@me ne .c] IMHO, foo.?bar should behave as "call-except-if-nil". Not only it
  |   | + 22180 [neleai@se na] IMHO foo.?bar should be same as (foo.bar rescue NoMethodError) to handle method_missing.
  |   | + 22219 [rogerdpack@g] IMHO there should be two methods, to avoid confusion, and they should
  |   |   22226 [radek.bulat@] Then how it is different from
  |   |   22230 [rogerdpack@g] You don't have to write foo and bar twice :)
  |   |   22232 [vjoel@pa h. ] Agree on both points. But what does the new method return?
  |   |   22234 [rogerdpack@g] I'm not sure.
  |   |   22236 [vjoel@pa h. ] Wouldn't it have to return some special object that simply didn't
  |   |   22237 [rogerdpack@g] Oh I gotcha.
  |   |   22239 [vjoel@pa h. ] Chaining would go like this then?
  |   |   22257 [hramrach@ce ] I think you are off the track here, at least WRT the original use of try.
  |   |   + 22259 [radek.bulat@] It doesn't convince me. It can lead to bad programming style and could
  |   |   | 22268 [hramrach@ce ] yes, I am aware of "rescue nil" possibly hiding different error than
  |   |   + 22309 [rogerdpack@g] Yeah chaining them would...still not be an option.  I
  |   |     22312 [hramrach@ce ] In this case I don't really care. I want to close the pipe if
  |   + 22181 [radek.bulat@] Don't you think that changes like this makes ruby more perlish? I
  + 21925 [rogerdpack@g] For me try's name is good but not perfect.
    21933 [dblack@ru yp] They're not really sub, though; they're just further messages. I think

[Bug #1123] DateTime.<=> is broken
21894 [redmine@ru y] Bug #1123: DateTime.<=> is broken

[Bug #1123] DateTime.<=> is broken
21897 [redmine@ru y] Issue #1123 has been updated by Daniel Luz.

[Bug #1124] Vista Unknown exception - code c0150014 with openFilenameDialog
21899 [redmine@ru y] Bug #1124: Vista Unknown exception - code c0150014 with openFilenameDialog

[Bug #1123] DateTime.<=> is broken
21900 [redmine@ru y] Issue #1123 has been updated by Rick DeNatale.

[Bug #1125] [*x] (array consisting only of a splat) does not necessarily return a new array
21901 [redmine@ru y] Bug #1125: [*x] (array consisting only of a splat) does not necessarily return a new array

[Bug #1126] make distclean error under MinGW
21902 [redmine@ru y] Bug #1126: make distclean error under MinGW

[Bug #1127] error while compiling Win32API under MinGW
21903 [redmine@ru y] Bug #1127: error while compiling Win32API under MinGW
21911 [rogerdpack@g] If it's any help, this error looks vaguely similar to the errors I
21914 [luislavena@g] Quotes in the prompt is something else, -e is not part of this error.

1.9 one-byte trace instruction and trap-instruction replacement?
21904 [rocky.bernst] Now that Ruby 1.9.1 has been released, if I recall correctly a
21966 [ko1@at ot ne] I want to impl. it till 1.9.2 as I said before.  But no roadmap.
21969 [rocky.bernst] Ok. I will look into providing a patch.
21970 [ko1@at ot ne] Seems great.  And revisiting debugger/profiler with this feature is also

[Bug #806] Net::Protocol#rbuf_fill is slow
21905 [redmine@ru y] Issue #806 has been updated by Jeremy Kemper.

[Bug #1127] error while compiling Win32API under MinGW
21906 [redmine@ru y] Issue #1127 has been updated by Alexey Borzenkov.

[Bug #1127] error while compiling Win32API under MinGW
21910 [redmine@ru y] Issue #1127 has been updated by Luis Lavena.

[Bug #1128] OptParse outputs a misleading display
21912 [redmine@ru y] Bug #1128: OptParse outputs a misleading display

[Bug #1128](Closed) OptParse outputs a misleading display
21913 [redmine@ru y] Issue #1128 has been updated by Nobuyoshi Nakada.

[Bug #1127] error while compiling Win32API under MinGW
21915 [redmine@ru y] Issue #1127 has been updated by Luis Lavena.

[Bug #1127] error while compiling Win32API under MinGW
21917 [redmine@ru y] Issue #1127 has been updated by Alexey Borzenkov.
+ 21918 [luislavena@g] unfortunate. :-/ I think quote_for_make is working really better, but oh we=
+ 21926 [rogerdpack@g] ev=3D21783 - in my opinion it doesn't cut the real root of the problem, but=

[Bug #1127] error while compiling Win32API under MinGW
21919 [redmine@ru y] Issue #1127 has been updated by Alexey Borzenkov.

[Bug #1127] error while compiling Win32API under MinGW
21920 [redmine@ru y] Issue #1127 has been updated by Alexey Borzenkov.

[Bug #1130] [PATCH] extern rb_thread_blocking_region_begin/end
21929 [redmine@ru y] Bug #1130: [PATCH] extern rb_thread_blocking_region_begin/end

[Bug #1130](Closed) [PATCH] extern rb_thread_blocking_region_begin/end
21930 [redmine@ru y] Issue #1130 has been updated by Nobuyoshi Nakada.

[Bug #1130] [PATCH] extern rb_thread_blocking_region_begin/end
21934 [redmine@ru y] Issue #1130 has been updated by Aman Gupta.

[Bug #1130] [PATCH] extern rb_thread_blocking_region_begin/end
21935 [redmine@ru y] Issue #1130 has been updated by Aman Gupta.

[Bug #1131] String#unpack("V") does not work correctly is linux on s390x
21937 [redmine@ru y] Bug #1131: String#unpack("V") does not work correctly is linux on s390x
21940 [nobu@ru y- a] System Z is 64bit big endian?  Could you show the config.h?

[Bug #1130](Closed) [PATCH] extern rb_thread_blocking_region_begin/end
21938 [redmine@ru y] Issue #1130 has been updated by Nobuyoshi Nakada.

[Bug #1131] String#unpack("V") does not work correctly is linux on s390x
21939 [redmine@ru y] Issue #1131 has been updated by Ittay Dror.

[Bug #119](Closed) Set#divide and SortedSet#divide raise NoMethodErrors when passed no block
21942 [redmine@ru y] Issue #119 has been updated by Akinori MUSHA.

Open Source Bridge Call for Proposals: We welcome your ideas (until March 31)
21943 [zznmeb@gm il] We are happy to announce that the Open Source Bridge Call for

[Bug #1134] [PATCH] Update racc runtime and fix warnings
21944 [redmine@ru y] Bug #1134: [PATCH] Update racc runtime and fix warnings
23791 [nobu@ru y- a] What warnings?
23811 [aaron@te de ] Sorry about this!  I was working off the parser.rb from the racc

MBARI patches on PPC and x86_64
21945 [brent@mb ri ] I've tested this February 9, 2009 compiling with GNUC targeting the
22044 [kingmt@gm il] I was attempting to backport your MBARI patches to 1.8.6 p287, which is what

New hash : syntax for the 1.8 series?
21946 [brent@mb ri ] I always liked the new hash symbol key colon syntax introduced in 1.9
+ 21947 [ruby-ml@ki t] I know the version boundary is not absolute, but I would very much
+ 21948 [shyouhei@ru ] ===================================================================
| 21983 [brent@mb ri ] Urabe,
| + 21984 [brent@mb ri ] Attached the complete parse.y by accident.
| | 22287 [knu@iD em ns] Thanks, I've done almost the same on ruby_1_8 and found a problem.
| + 22012 [shyouhei@ru ] Oops, I was not aware of this error.  Thank you pointing it out.
+ 21949 [knu@iD em ns] Yes.  Backporting syntactic changes is a big part of the plan for ruby
| + 21950 [murphy@ru yc] the confusion created by backporting more and more of Ruby 1.9 to 1.8 is
| | 21956 [knu@iD em ns] I may have redefined the meaning of teeny, but I think that the
| + 21951 [ruby-ml@ki t] I personally feel this is not the best course of action. I see no
| | 21959 [knu@iD em ns] We provide ruby_1_8_6 and ruby_1_8_7 branches (patch releases) for
| | 21960 [dblack@ru yp] Could we call 1.8.8 "1.9.-1"? :-) I think a lot of people are getting
| + 21952 [dblack@ru yp] The problem is, though, that if a customer says, "We will only run
|   + 21961 [shyouhei@ru ] Every single ruby release was a bridge version for ruby 2.0 anyway; take a look
|   | 21965 [charles.nutt] I hope there's some consideration for alternative implementations as
|   | + 21975 [shyouhei@ru ] I, as one of a mentor of "alternative implementations" than matz's 1.9, know so
|   | + 21978 [zznmeb@gm il] Most of the people that I know running production Ruby environments
|   | + 22031 [akinori.mush] =begin
|   + 21963 [knu@iD em ns] Agreed.  Maybe it's time to (re)define the versioning scheme.  As I
|     21977 [evan@fa li g] I would hope that some consideration is given to how people expect
|     + 21979 [zznmeb@gm il] I am much less concerned about the numbers than I am about the
|     + 21980 [matz@ru y- a] As for 1.8.7, it was unfortunate to break Rails at the beginning, but
|     | + 21985 [radek.bulat@] s?"
|     | | + 21991 [pit.capitain] I've been one of them until today. Having to stay at home a couple of
|     | | | 21996 [radek.bulat@] Good for you :). But I repeat it again: it's only one side of the
|     | | | 22009 [pit.capitain] Many people have claimed this, but no one has shown examples for this yet.
|     | | | 22011 [Daniel.Berge] =20
|     | | | + 22021 [dooby@d1 .k ] (3) Please set environment variable (({INCLUDE})), (({LIB})), (({PATH}))
|     | | | + 22022 [nobu@ru y- a] Use Windows bundled find.exe, not of msys or cygwin.
|     | | + 21993 [james@gr yp ] I agree.
|     | |   21995 [gregory.t.br] in
|     | + 21992 [zznmeb@gm il] Programming is as much, if not more, about communications within a team
|     + 21981 [akinori.mush] I'm using Gmail because the mail server I have been using is down right now...
|     + 22001 [pbrannan@at ] Why not Ruby 2000? :)
+ 21957 [Daniel.Berge] h =3D {dog: :bark}

[Bug #1135] Problem renaming CMath.hypot in Ruby1.9
21953 [redmine@ru y] Bug #1135: Problem renaming CMath.hypot in Ruby1.9

[Bug #1136] "ri Kernel#require" is broken
21954 [redmine@ru y] Bug #1136: "ri Kernel#require" is broken
21955 [murphy@ru yc] $ gem uninstall rails

ruby 1.9.1 parallel make race
21958 [andrew@wa ro] Nice work on 1.9.; I've just starting porting my stuff across and like
21974 [andrew@wa ro] ...
+ 21976 [andrew@wa ro] Sorry - cut-n-paste mistake. The mkdir rule is of course
+ 21990 [andrew@wa ro] UPDATE

[Bug #1139] Segmentation fault ruby 1.9.1p0 (2009-01-30 revision 21907)
21962 [redmine@ru y] Bug #1139: Segmentation fault ruby 1.9.1p0 (2009-01-30 revision 21907)
21971 [ko1@at ot ne] Could you show your program, or make short reproduce-able script?

[Bug #1140] Parsing error gives method_missing a nonexistant method name
21964 [redmine@ru y] Bug #1140: Parsing error gives method_missing a nonexistant method name

[Bug #1141] assignment of variable in "right" if statement fails
21967 [redmine@ru y] Bug #1141: assignment of variable in "right" if statement fails

[Bug #1140] Parsing error gives method_missing a nonexistant method name
21982 [redmine@ru y] Issue #1140 has been updated by Pit Capitain.

UTF-16BE is alias for UCS-2BE - is this correct?
21986 [radek.bulat@] I've played with new encoding stuff from ruby1.9.1 and have noticed
21987 [naruse@ai em] Strictly it is of course incorrect.

[Bug #1127] error while compiling Win32API under MinGW
21988 [redmine@ru y] Issue #1127 has been updated by Alexey Borzenkov.
22003 [luislavena@g] und that it already contains mkintpath. So, sorry for all I said earlier, e=

[Bug #1142] /opt/ruby19/lib/ruby19/1.9.1/openssl/ssl.rb:31: [BUG] Bus Error
21989 [redmine@ru y] Bug #1142: /opt/ruby19/lib/ruby19/1.9.1/openssl/ssl.rb:31: [BUG] Bus Error

[Bug #835](Closed) fix for Documentation on ruby*/lib/benchmark
21994 [redmine@ru y] Issue #835 has been updated by Kentaro Goto.

1.8.7 Specifics
21997 [jbarnette@gm] There's a fair amount of talk lately about release management and
+ 21999 [luislavena@g] segmentation faults with FXRuby and wxRuby, which I believe those
| 22004 [charles.nutt] FWIW, parsetree-like tools are *always* going to face this problem from
| + 22005 [luislavena@g] Thank you Charles for sharing the point of view from JRuby side.
| | + 22006 [charles.nutt] We're very worried about the same thing, and even worse worried about
| | + 22007 [pit.capitain] AFAIR there always have been problems like this moving from one Ruby
| |   22008 [matz@ru y- a] Perhaps, people became less geek these days.
| |   + 22010 [hramrach@ce ] Or perhaps it was because those changes were few and introduced to fix
| |   | 22015 [jbarnette@gm] All,
| |   | 22020 [hramrach@ce ] Some methods in 1.8.7 return Enumerator instead of an Array. This adds
| |   | 22023 [akinori.mush] Would you please name an example?
| |   | 22038 [hramrach@ce ] File.open("2.6.28-rc6-rc7.patch"){|f|f.lines[1..3]}
| |   | 22039 [akinori.mush] Ruby 1.8.6 did not have {IO,File}#lines.  It first appeared in 1.8.7
| |   | 22043 [hramrach@ce ] Yes, there is no IO#lines in 1.8.6.
| |   + 22019 [ezmobius@gm ] Or perhaps there are *far* more folks running their businesses in
| |   + 22024 [brent@mb ri ] Matz,
| |     22025 [matz@ru y- a] The current 1.8.6 maintainer Shyouhei sitting next to me right now,
| |     + 22028 [ezmobius@gm ] Matz & Shyouhei
| |     | + 22034 [charles.nutt] Whoever takes over as maintainer should include alternative implementers
| |     | | 22042 [ezmobius@gm ] Charlie-
| |     | + 22048 [shyouhei@ru ] Thank you for a great offer.  Unless anyone else has an intention, it is OK
| |     |   22049 [ezmobius@gm ] Thank you Matz and Shyouhei, we promise to take very good care of your
| |     + 22041 [gregory.t.br] I think this is a great idea, Matz.    I fully plan to use Ruby 1.9.1
| + 22016 [ryand-ruby@z] not true. I no longer have a maintenance issue with 1.9.0+. :/
+ 22000 [gregory.t.br] When I initially tried running Ruport's tests on 1.8.7, there were
| 22014 [aaron@te de ] I can't agree with this at all.  If you refuse to run your tests
| 22017 [gregory.t.br] I don't support 1.8.7.  The issue is that people can fairly easily
| 22057 [zznmeb@gm il] That's an interesting option, given that Engine Yard has volunteered to
| 22082 [gregory.t.br] I have considered this option but didn't want to stand in front of an
| 22085 [ruby-ml@ki t] I think it is a perfectly acceptable and in my opinion,
| + 22092 [ksankar@ci c] One good thing is that there is precedence. We can follow Python's 3.0 path. A clear roadmap for transition, well documented porting plan as well as volunteer support for 1.8.x would work.
| + 22148 [pit.capitain] You don't have to do anything special. Just develop your code for
+ 22334 [calcifer@ru ] Sorry for a little late response... So, i have one small story, from several
  + 22341 [nobu@ru y- a] Could you elaborate?  The change was to accept a block if no
  + 22344 [knu@iD em ns] That sets me wondering.  You might have been either giving both an
    + 22359 [hramrach@ce ] Well, this file is quite lengthy and not very readable even for those
    | 22360 [knu@iD em ns] I agree that the file has many points to improve, but the section
    | + 22362 [ruby-ml@ki t] The NEWS file is pretty good both in 1.8.7 and 1.9.1, but I think
    | + 22364 [hramrach@ce ] Thanks.
    + 22558 [calcifer@ru ] charset="iso-8859-15"
threads.html
top