Return-Path: X-Original-To: apmail-jackrabbit-oak-dev-archive@minotaur.apache.org Delivered-To: apmail-jackrabbit-oak-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8AB0CE2B6 for ; Thu, 17 Jan 2013 13:44:05 +0000 (UTC) Received: (qmail 74618 invoked by uid 500); 17 Jan 2013 13:44:05 -0000 Delivered-To: apmail-jackrabbit-oak-dev-archive@jackrabbit.apache.org Received: (qmail 74498 invoked by uid 500); 17 Jan 2013 13:44:04 -0000 Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: oak-dev@jackrabbit.apache.org Delivered-To: mailing list oak-dev@jackrabbit.apache.org Received: (qmail 74470 invoked by uid 99); 17 Jan 2013 13:44:03 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 13:44:03 +0000 Received: from localhost (HELO mail-oa0-f44.google.com) (127.0.0.1) (smtp-auth username bdelacretaz, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 13:44:03 +0000 Received: by mail-oa0-f44.google.com with SMTP id n5so2644098oag.31 for ; Thu, 17 Jan 2013 05:44:02 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.60.1.132 with SMTP id 4mr3805349oem.140.1358430242150; Thu, 17 Jan 2013 05:44:02 -0800 (PST) Received: by 10.76.69.138 with HTTP; Thu, 17 Jan 2013 05:44:02 -0800 (PST) In-Reply-To: <1D543B2C-50A3-4BD5-B859-0B89D3648F5F@adobe.com> References: <1D543B2C-50A3-4BD5-B859-0B89D3648F5F@adobe.com> Date: Thu, 17 Jan 2013 14:44:02 +0100 Message-ID: Subject: Re: MongoMicroKernel concurrency issue From: Bertrand Delacretaz To: oak-dev@jackrabbit.apache.org Content-Type: text/plain; charset=UTF-8 On Thu, Jan 17, 2013 at 11:57 AM, Damien Obrist wrote: > ...I didn't forget to attach it but somehow it got lost on the way. Here is my second try... Many @apache.org lists are configured to strip attachments, that's probably the case here - better create a jira issue and attach your patch there. -Bertrand