doh forget the last part. coffee is needed :)
On Thu, Nov 1, 2012 at 7:02 AM, Benoit Chesneau wrote:
>
>
>
> On Thu, Nov 1, 2012 at 6:52 AM, Adam Kocoloski wrote:
>
>> On Nov 1, 2012, at 1:41 AM, Benoit Chesneau wrote:
>>
>> > ok I will stop for now pushed 431_feature_cors (the removing of cap
On Thu, Nov 1, 2012 at 6:52 AM, Adam Kocoloski wrote:
> On Nov 1, 2012, at 1:41 AM, Benoit Chesneau wrote:
>
> > ok I will stop for now pushed 431_feature_cors (the removing of caps is
> > wanted here and I will be happy to just update the jira title if someone
> > really care) .
>
> Sure, I onl
On Nov 1, 2012, at 1:41 AM, Benoit Chesneau wrote:
> ok I will stop for now pushed 431_feature_cors (the removing of caps is
> wanted here and I will be happy to just update the jira title if someone
> really care) .
Sure, I only used caps because CORS is an acronym. It doesn't matter at all.
ok I will stop for now pushed 431_feature_cors (the removing of caps is
wanted here and I will be happy to just update the jira title if someone
really care) .
Side note: Imo adding feature in the naming here doesn't give anything .
Prefixing by feature/ at least would optimize queries for rapid
that's naming is really awkward should be feature/431-cors (why keeping
caps?) . Anyway changing it again.
On Thu, Nov 1, 2012 at 6:33 AM, Adam Kocoloski wrote:
> Benoit, sorry to keep nagging, but one of the specific conclusions of the
> thread on branch naming that you started earlier today
Benoit, sorry to keep nagging, but one of the specific conclusions of the
thread on branch naming that you started earlier today was that the branch name
should indicate whether it's a *feature* or a *bugfix*. In this case the
syntax would be 431-feature-CORS.
Adam
On Nov 1, 2012, at 1:30 AM,
The branch have been renamed to 431_cors. I'm not sure it will be renamed
on github too.
- benoit
On Thu, Nov 1, 2012 at 5:34 AM, Paul Davis wrote:
> On Wed, Oct 31, 2012 at 8:14 PM, Adam Kocoloski
> wrote:
> > Right, the wiki page for this stuff is
> http://wiki.apache.org/couchdb/Merge_Proce
On Wed, Oct 31, 2012 at 8:14 PM, Adam Kocoloski wrote:
> Right, the wiki page for this stuff is
> http://wiki.apache.org/couchdb/Merge_Procedure which now reads
>
>> Please use the ticket number, the type of the branch, along with a very
>> short descriptive phrase, for your branch name.
>>
>> I
Right, the wiki page for this stuff is
http://wiki.apache.org/couchdb/Merge_Procedure which now reads
> Please use the ticket number, the type of the branch, along with a very short
> descriptive phrase, for your branch name.
>
> If the ticket was COUCHDB-1234, and the ticket title was My Cool
hr i thought it was ticketnumber_shortdescr I didn't read last
update of the wiki though ..
- benoît
On Thu, Nov 1, 2012 at 12:50 AM, Adam Kocoloski wrote:
> A minor thing -- didn't we just propose earlier today to use a naming
> convention like 431-feature-CORS for these topic branche
A minor thing -- didn't we just propose earlier today to use a naming
convention like 431-feature-CORS for these topic branches?
Adam
On Oct 31, 2012, at 7:43 PM, beno...@apache.org wrote:
> Updated Branches:
> refs/heads/COUCHDB-431_cors [created] 0777262fa
>
>
> handle CORS. fix #COUCHDB-4
11 matches
Mail list logo
