Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 48188 invoked from network); 26 Jun 2009 17:40:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 Jun 2009 17:40:51 -0000 Received: (qmail 4715 invoked by uid 500); 26 Jun 2009 17:41:01 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 4659 invoked by uid 500); 26 Jun 2009 17:41:01 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 4649 invoked by uid 99); 26 Jun 2009 17:41:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Jun 2009 17:41:01 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.216.171] (HELO mail-px0-f171.google.com) (209.85.216.171) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Jun 2009 17:40:50 +0000 Received: by pxi1 with SMTP id 1so1902457pxi.5 for ; Fri, 26 Jun 2009 10:40:29 -0700 (PDT) Received: by 10.114.66.10 with SMTP id o10mr6152123waa.33.1246038029450; Fri, 26 Jun 2009 10:40:29 -0700 (PDT) Received: from ?192.168.42.100? (75-101-123-136.dsl.static.sonic.net [75.101.123.136]) by mx.google.com with ESMTPS id n33sm6343497wag.21.2009.06.26.10.40.27 (version=SSLv3 cipher=RC4-MD5); Fri, 26 Jun 2009 10:40:28 -0700 (PDT) Message-ID: <4A4507DE.3040602@cloudera.com> Date: Fri, 26 Jun 2009 10:39:42 -0700 From: Amr Awadallah Organization: Cloudera, Inc. User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: core-dev@hadoop.apache.org Subject: Re: more information about project split References: <4A400358.3070703@yahoo-inc.com> <4A400827.3090409@apache.org> <4A402377.50107@cloudera.com> <3A42F667-2FB8-42BC-A77D-9A8B1A906171@apache.org> <4A411FB3.3010004@apache.org> <4A419FDC.6090304@cloudera.com> <4aa34eb70906232247h16196524gece90ff1e88d4ad5@mail.gmail.com> <4A437851.8040500@apache.org> <4A44FF7E.2040705@cloudera.com> <4A450342.4030306@apache.org> In-Reply-To: <4A450342.4030306@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org > Does this meet your needs? Doug, The way you describe it below works great for me, I must have misunderstood what (4) means, from Owen's email it said: > 4. all to dev as opposed to create/resolve to dev, and all to issues (which I am totally ok with and would work great for me). Thanks, -- amr Doug Cutting wrote: > Amr Awadallah wrote: >> To re-iterate, not all JIRAs are imporant to me, there are some key >> ones that I would like to get all updates on, and there are others >> that I would just like to check once in a while but don't really have >> capacity to be getting email updates for. How do we accommodate that? > > I think the currently favored proposal (4) can meet your needs. Under > this, Jira will only send messages to the -dev list when issues are > created or resolved. All other Jira messages will go to just the > -issues list. (Commits are already routed only to the -commits list.) > > You would subscribe to the -dev list but not the -issues list. On > seeing a create message, you can elect in Jira to watch an issue to > receive all updates to that issue. Folks who want to see all issue > updates might subscribe to the -issues and -commits lists as well. > > Does this meet your needs? > > Doug