[#686] Wall compilation — Michal Rokos <michal@...>
Hi everybody,
[#688] mkmf.rb - add files to clean and distclean targets — Michal Rokos <michal@...>
Hi,
On Thu, 16 Jan 2003, Michal Rokos wrote:
Hi,
Hi,
On Tue, Jan 21, 2003 at 11:16:39AM +0900, Yukihiro Matsumoto wrote:
Hi,
On Tue, Jan 21, 2003 at 06:38:00PM +0900, Yukihiro Matsumoto wrote:
Hi,
On Tue, Jan 21, 2003 at 11:37:35PM +0900, Yukihiro Matsumoto wrote:
Hi,
Hello,
Hi,
Hi,
Hi,
Hi,
[#708] Documentation for thread.rb — Gavin Sinclair <gsinclair@...>
Hi ruby-core,
[#719] nd_end and NODE_NEWLINE (fwd) — Chad Fowler <chad@...>
[#724] Symbols: More Functionality Wanted — Ryan Pavlik <rpav@...>
I've been discussing this for a bit on #ruby-lang on OPN (or freenode or
Hi,
On 20 Jan 2003 at 15:49, Yukihiro Matsumoto wrote:
Hi --
On Thursday, January 23, 2003, 6:28:04 AM, dblack wrote:
Gavin Sinclair <gsinclair@soyabean.com.au> writes:
Hi,
matz@ruby-lang.org (Yukihiro Matsumoto) writes:
Hi,
On Fri, 24 Jan 2003 03:34:46 +0900
[#730] Comments on matrix.rb — Gavin Sinclair <gsinclair@...>
Hi -core,
[#757] Extensions for Time and ParseDate — Ryan Davis <ryand-ruby@...>
Eric and I have been hacking around and we can't stand the lack of
[#759] Adding Test::Unit to CVS — "Nathaniel Talbott" <nathaniel@...>
Matz has already given me the go-ahead to add Test::Unit to CVS, but I
Nathaniel Talbott wrote:
On Wednesday, January 22, 2003, at 07:56 AM, Dave Thomas wrote:
Re: Adding Test::Unit to CVS
At Wed, 22 Jan 2003 14:31:06 +0900,
Nathaniel Talbott wrote:
> isn't a good place for the Test::Unit tests to go (yet). Thus, I'm
> planning on importing Test::Unit, using something like the following:
>
> cvs -d:pserver:ntalbott@cvs.ruby-lang.org:/src import -Ipre-install.rb
> -m "Imported Test::Unit 0.1.6" ruby/lib testunit testunit_0-1-6
>
> Now, I just discovered this command tonight, so maybe it isn't a good
> way to do this. What I see as the advantage, though, is that then I can
> just re-import every time I release a new version of Test::Unit, and the
> main ruby distro won't be affected by bugs (yes, even with testing I
> still introduce bugs <sigh>) that I may create in active development.
The procedure is OK. You can keep developing the module in the rough/
tree and import every stable release snapshot into ruby/lib/ for 1.8
and into shim/ruby16/lib/ for 1.6.
By the way, would you convert the indentation of the Test::Unit files
from tab to 2-space? Our standard coding convention requires 2-space
indentation. Perhaps just adding some editor directives for emacs and
vi will do, though.
Regards,
--
/
/__ __ Akinori.org / MUSHA.org
/ ) ) ) ) / FreeBSD.org / Ruby-lang.org
Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp
"It went right by me -- At the time it went over my head
I was looking out the window.. I should have looked at your face instead"