Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 01BEA431FBC for ; Fri, 20 Nov 2009 07:17:01 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2MyJTVdUswce for ; Fri, 20 Nov 2009 07:17:00 -0800 (PST) Received: from azsmga102.ch.intel.com (mga12.intel.com [143.182.124.36]) by olra.theworths.org (Postfix) with ESMTP id 1714B431FAE for ; Fri, 20 Nov 2009 07:16:59 -0800 (PST) Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga102.ch.intel.com with ESMTP; 20 Nov 2009 07:16:59 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.44,777,1249282800"; d="scan'208";a="213880172" Received: from unknown (HELO cwilso3-mobl.ger.corp.intel.com) ([10.255.16.184]) by azsmga001.ch.intel.com with SMTP; 20 Nov 2009 07:16:57 -0800 Received: by cwilso3-mobl.ger.corp.intel.com (sSMTP sendmail emulation); Fri, 20 Nov 2009 15:15:16 +0000 Content-Type: text/plain; charset=UTF-8 From: Chris Wilson To: Jan Janak In-reply-to: References: Date: Fri, 20 Nov 2009 15:15:16 +0000 Message-Id: <1258729976-sup-5984@broadwater.alporthouse.com> User-Agent: Sup/git Content-Transfer-Encoding: 8bit Cc: Not Much Mail Subject: Re: [notmuch] Recommended Coding Style? X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2009 15:17:01 -0000 Excerpts from Jan Janak's message of Fri Nov 20 15:08:31 +0000 2009: > Is there any recommended coding style for the C/C++ code in notmuch? My prediction is that Carl will go with something close to what he wrote for Cairo: http://cgit.freedesktop.org/cairo/tree/CODING_STYLE He may or may not change to a more kernel style, but he definitely will not mandate 3-space indents. ;-) -ickle -- Chris Wilson, Intel Open Source Technology Centre