Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 86699 invoked from network); 30 Nov 2010 13:33:02 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Nov 2010 13:33:02 -0000 Received: (qmail 83570 invoked by uid 500); 30 Nov 2010 13:33:02 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 83533 invoked by uid 500); 30 Nov 2010 13:33:02 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 83525 invoked by uid 99); 30 Nov 2010 13:33:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Nov 2010 13:33:01 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bchesneau@gmail.com designates 209.85.214.180 as permitted sender) Received: from [209.85.214.180] (HELO mail-iw0-f180.google.com) (209.85.214.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Nov 2010 13:32:55 +0000 Received: by iwn37 with SMTP id 37so7093361iwn.11 for ; Tue, 30 Nov 2010 05:32:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=7ytJpKkeuETDjktKduRKuiCz7EfDD0WJrtGqLfYrZu0=; b=q5zG4Uqs2ZHWd1teVBsUjzKk7D+ZrmlmupVomlwiHg4/Q0dqDp9dejKUcpxn2iDb35 3JWiike80ERnfFyT/tdhnai8qGZwWprte0769iPlMeyAeD+kaVuW+5dtPAC3+OVDMVD/ XUntkIgRUtguiai48RhM0FC1EBANq85SroFRk= 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=E3fN9ndDImaChteWcGYFXjjEdcOeG4tf/OvGFZknmZpJFPgq33NAUmhH0Y30EyQ6Gh 8EbtlGbw7NIFO3qbLZqG4NFuIT0P0UjcOCGyuRx/Vs0qn9zWr8LZLHKp56/eNN+p0fwW s7nGgl182tvl9wgot8+i5jwVKrXPNhPs32U+Q= MIME-Version: 1.0 Received: by 10.231.10.137 with SMTP id p9mr7328648ibp.186.1291123954562; Tue, 30 Nov 2010 05:32:34 -0800 (PST) Received: by 10.231.50.70 with HTTP; Tue, 30 Nov 2010 05:32:34 -0800 (PST) In-Reply-To: References: Date: Tue, 30 Nov 2010 14:32:34 +0100 Message-ID: Subject: Re: use view functions to emit changes From: Benoit Chesneau To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Nov 30, 2010 at 1:50 PM, Jan Lehnardt wrote: > > On 30 Nov 2010, at 13:05, Benoit Chesneau wrote: > >> On Tue, Nov 30, 2010 at 12:22 PM, Filipe David Manana >> wrote: >>> >>> 3) Avoid the unnecessary white-space only changes: >>> >>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623d= ae89bf9a5ad#L2R396 >>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623d= ae89bf9a5ad#L2R477 >>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623d= ae89bf9a5ad#L3R255 >>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623d= ae89bf9a5ad#L4R60 >>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623d= ae89bf9a5ad#L4R85 >>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623d= ae89bf9a5ad#L4R247 >>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623d= ae89bf9a5ad#L4R503 >>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623d= ae89bf9a5ad#L3R191 >> >> >> about 2 & 3 can we add indent rules on top of our sources from now ? >> I think there is something common between vim and emacs for example. >> That should solve such errors. I don't want to change my config each >> time I'm using a project. Using such rules solves that automatically. >> >> Ex: >> >> %% -*- tab-width: 4;erlang-indent-level: 4;indent-tabs-mode: nil -*- >> %% ex: ts=3D4 sw=3D4 et >> >> works on erlang and vim and surely other editors. > > a) I don't mind adding these markers they it help anyone. > b) My editor and git tell me about trailing whitespace. > c) Because of b), these markers never helped me. > >> About the 2 spaces >> in js, imo we should go to a 4 spaces indentations, which is a way >> more readable and more common. (Mozilla uses that rule.) > > We agreed on two spaces early on: > > =A0http://wiki.apache.org/couchdb/Coding_Standards > > Coding standards are not to find the best one, but to pick one and > stick to it. > Coding standard are here to make the code more easy to share *between* developers, this isn't just a convention. Sorry to disagree with the 2 spaces indentation. While we are in coding standard , there is one I really think we should follow "http://www.erlang.se/doc/programming_rules.shtml#REF14536" . I think I can add for some, but need help for btree codes and view server, anyone can help me on that ? - beno=EEt.