Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3564710CD7 for ; Wed, 29 Jan 2014 10:11:47 +0000 (UTC) Received: (qmail 91261 invoked by uid 500); 29 Jan 2014 10:11:46 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 90844 invoked by uid 500); 29 Jan 2014 10:11:45 -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 90824 invoked by uid 99); 29 Jan 2014 10:11:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jan 2014 10:11:45 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bchesneau@gmail.com designates 209.85.216.182 as permitted sender) Received: from [209.85.216.182] (HELO mail-qc0-f182.google.com) (209.85.216.182) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jan 2014 10:11:40 +0000 Received: by mail-qc0-f182.google.com with SMTP id c9so2344830qcz.41 for ; Wed, 29 Jan 2014 02:11:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=kcUyQvjRw3tWg3+VvOh3eN6p8/ZLDgiNiL3aFLDjKhw=; b=LWSdr6OsNbB/i2oxncAIHWlD7kga7E+dCNTYLy6erdoKYCIoc3GqJRkOWDuMFxNl7d cA21HvV+7dzL8n8O5QoRhEn+rrvnasetEGyfkvRmK35tdy167mIZeB/WH0a2kiV0pRxg mJR/CURLlZ1i45i9prN/WSDUUghJk2Y9wiGQ6HlPY36tTXBt8eQNhtQHwyMAteTg4DXL 7vqg4rmnQI59oShcSugOBioFz2M+ixgHPksZfTxIKtfMsJOo2kktv9pDxc/dsGpaqT+r Ad2TAadb/4n0lIDhqkwK4QXmBq9Hb6xkE6PC/XztHF5c87074lVBSbd497rYBXthl2/5 nbvg== X-Received: by 10.224.157.7 with SMTP id z7mr10429760qaw.37.1390990280123; Wed, 29 Jan 2014 02:11:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.96.58.195 with HTTP; Wed, 29 Jan 2014 02:11:00 -0800 (PST) In-Reply-To: References: From: Benoit Chesneau Date: Wed, 29 Jan 2014 11:11:00 +0100 Message-ID: Subject: Re: can fauxton commit be tagged? To: "dev@couchdb.apache.org" Content-Type: multipart/alternative; boundary=089e0160a3d0886d5c04f119295f X-Virus-Checked: Checked by ClamAV on apache.org --089e0160a3d0886d5c04f119295f Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jan 29, 2014 at 10:55 AM, Benoit Chesneau wrote: > There are a lot of fauxton commits landing in master. Which is fine I > guess but that makes it hard to check other commits. Can you eventually tag > them with "fauxton:" or whatever saying fauxton. It will be a lot easier > to filter when looking for other patches. > > Thanks! > > - benoit > > > Just an example, the list of 60 patches I have to apply since I started the rcouch merge branch: https://www.friendpaste.com/7voDrcGTN0IY5rSfDCrQE Most are related to fauxton :) - benoit --089e0160a3d0886d5c04f119295f--