Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of bchesneau@gmail.com
 designates 209.85.210.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAJNb-9pRQErx7VZUdWM-tkwXidBikR8QV6+h=Ywak3nNp1uOOg@mail.gmail.com>
References: <20121031234336.4B0DB5154F@tyr.zones.apache.org>
	<57B93226-49D4-4F20-9991-AC8A50A7F39D@apache.org>
	<CAJNb-9pMEwxusvCBpPW3AoJzmuxYRoQpCqgcmjNLS-=ZkRGXgw@mail.gmail.com>
	<26DCFB09-C3A7-4596-8B5E-4E7E40B61BF4@apache.org>
	<CAJ_m3YDV2WPBZbjD2oW_oePy+oEF0F60bS5bDaoOMmy4bJC3Ug@mail.gmail.com>
	<CAJNb-9oMAyJ=ZJB7+HO-wxAu0+rGUcOsrA2tkbWxo-B-x-x6QQ@mail.gmail.com>
	<6BC31E10-AA09-4A2C-B6F1-F29DA2DB8290@apache.org>
	<CAJNb-9ottkHXzqGYFdTWUOZG_quWcsrMJ5HCge+zuE8U9bicMg@mail.gmail.com>
	<CAJNb-9roqi_4Hjr07BCjJzsbT1x8XoPouQA44o0qFwxMEZPXhw@mail.gmail.com>
	<C4E2DB0A-F29D-456A-AFF7-DE09A3E7AF5A@apache.org>
	<CAJNb-9pRQErx7VZUdWM-tkwXidBikR8QV6+h=Ywak3nNp1uOOg@mail.gmail.com>
Date: Thu, 1 Nov 2012 07:03:41 +0100
Message-ID: 
 <CAJNb-9rUrf-kzGOv6Jix4GnFBvUACSGRDVAda4fB3e2=aCDN1A@mail.gmail.com>
Subject: Re: git commit: handle CORS. fix #COUCHDB-431
From: Benoit Chesneau <bchesneau@gmail.com>
To: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Content-Type: multipart/alternative; boundary=f46d04446969ed4f1504cd68c76d

--f46d04446969ed4f1504cd68c76d
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

doh forget the last part. coffee is needed :)


On Thu, Nov 1, 2012 at 7:02 AM, Benoit Chesneau <bchesneau@gmail.com> wrote=
:

>
>
>
> On Thu, Nov 1, 2012 at 6:52 AM, Adam Kocoloski <kocolosk@apache.org>wrote=
:
>
>> On Nov 1, 2012, at 1:41 AM, Benoit Chesneau <bchesneau@gmail.com> wrote:
>>
>> > ok I will stop for now pushed 431_feature_cors (the removing of caps i=
s
>> > wanted here and I will be happy to just update the jira title if someo=
ne
>> > really care) .
>>
>> Sure, I only used caps because CORS is an acronym.  It doesn't matter at
>> all.  Is there a reason why you keep using underscores instead of hyphen=
s?
>>
>> > Side note: Imo adding feature in the naming here doesn't give anything
>>  .
>> > Prefixing by feature/ at least would optimize queries for rapid eye
>> looking
>> > or a bot going over the issues...
>>
>> Probably best to bring that up as an objection to Jan's proposal in the
>> "branching in couchdb" thread.  Personally I prefer the 431-feature-cors
>> style from that proposal.
>>
>
> I'm doing it now. The point of using feature/ and fix/ is to help later
> when we will all works actively on different features/ fixes/ and the
> number of branch will be larger. Using XXX-feature_... will not help at a=
ll
> in this case. I know this isn't a problem today but I prefer having a
> strict naming like this at first rather than trying to change things late=
r.
> Especially since this is a known problem.
>
>
>
>> I realize I'm being incredibly pedantic, but it just rubbed me the wrong
>> way that we collectively wrote 9 emails on the topic branch naming today=
,
>> got what appeared to be lazy consensus on a convention, and then almost
>> immediately ignored that convention.  Regards,
>>
>
> That wasn't intended. I may have missed that we reached a consensus on a
> new naming. For hyphen and such well... I will fix it again, though i thi=
nk
> using - helps to separate meanings when _ is normally used to extend a
> meaning of the same info (here ticket number vs short description) .
>
> - beno=EEt
>

--f46d04446969ed4f1504cd68c76d--