Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion node-v0.1.30

X-BeenThere: nodejs@googlegroups.com
Received: by 10.231.117.207 with SMTP id s15ls300036ibq.2.p; Thu, 25 Feb 2010 
	13:04:35 -0800 (PST)
Received: by 10.231.146.4 with SMTP id f4mr5637ibv.13.1267131875803;
        Thu, 25 Feb 2010 13:04:35 -0800 (PST)
Received: by 10.231.146.4 with SMTP id f4mr5636ibv.13.1267131875780;
        Thu, 25 Feb 2010 13:04:35 -0800 (PST)
Return-Path: <coldredle...@gmail.com>
Received: from mail-gw0-f53.google.com (mail-gw0-f53.google.com [74.125.83.53])
        by gmr-mx.google.com with ESMTP id 19si707365ywh.4.2010.02.25.13.04.34;
        Thu, 25 Feb 2010 13:04:34 -0800 (PST)
Received-SPF: pass (google.com: domain of coldredle...@gmail.com designates 74.125.83.53 as permitted sender) client-ip=74.125.83.53;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of coldredle...@gmail.com designates 74.125.83.53 as permitted sender) smtp.mail=coldredle...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by mail-gw0-f53.google.com with SMTP id 19so153444gwj.26
        for <nodejs@googlegroups.com>; Thu, 25 Feb 2010 13:04:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        bh=dp531LaGybh/tS+T8fcEdbErE5uy1Y3yPA+uoRmYsqI=;
        b=PfB8nB6AQKJ5jbfKITYPxaFjbYZhKZ07krzTNlaqMfvQaNSMT+1Bsb+LRkNwuiQXv2
         WWvC7tmPbUy4soHcrsOHNkhjHERhsUJHsesd/KHS5u5T1QYzXJuys+Y7iRbQeZOwkPy2
         C2Mfd7DRNrGXcCFvGDeJ3Nzc9Ykp17A6d5ib4=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=TUq9mj/2joivA7KdhiWwBKsoble9d743//1QA3vCgiRPEM4KhdyEup4AVHt/q0wXOH
         NZRJEe/acUO3D9QxZ5YDOBie58FD8BpVCCu9KYfFcLlJAkhywW2oMYeJpkKfmEqRTQIA
         K2HjSorGKsTdvKKYVOdCic9P5l926QYGzDIxM=
MIME-Version: 1.0
Received: by 10.101.12.6 with SMTP id p6mr497620ani.248.1267131874279; Thu, 25 
	Feb 2010 13:04:34 -0800 (PST)
In-Reply-To: <8498cdd51002251257j37ef86d3rb125aa8962c1e...@mail.gmail.com>
References: <21ee31951002220137h353828c4yffedc68949feb...@mail.gmail.com>
	 <5c02bc4e1002220839y981fe55w156c9cbeefe86...@mail.gmail.com>
	 <8498cdd51002242358h20649838t7acd8d0173f73...@mail.gmail.com>
	 <8498cdd51002251257j37ef86d3rb125aa8962c1e...@mail.gmail.com>
Date: Thu, 25 Feb 2010 13:04:34 -0800
Message-ID: <21ee31951002251304j20ee7c53vfb65dffaf3620...@mail.gmail.com>
Subject: Re: [nodejs] node-v0.1.30
From: Ryan Dahl <coldredle...@gmail.com>
To: nodejs@googlegroups.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 25, 2010 at 12:57 PM, Benjamin Thomas <bam.tho...@gmail.com> wr=
ote:
> I've updated the patch to properly merge with the test changes that
> were just pushed.
>
> I fully acknowledge that this is a bike-shedding issue. =C2=A0Seems like
> now is the time to do it if you are considering it because the API is
> already going through a lot of change anyway. =C2=A0Easier now than later=
.

I agree, it's a better name. I like saving the two characters. landed
in b1b84960cedcbc033b28c0644beada614b006a9b