Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-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 020A817544 for ; Wed, 22 Apr 2015 20:13:54 +0000 (UTC) Received: (qmail 28940 invoked by uid 500); 22 Apr 2015 20:13:53 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 28862 invoked by uid 500); 22 Apr 2015 20:13:53 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 28294 invoked by uid 99); 22 Apr 2015 20:13:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Apr 2015 20:13:52 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: message received from 54.191.145.13 which is an MX secondary for dev@hbase.apache.org) Received: from [54.191.145.13] (HELO mx1-us-west.apache.org) (54.191.145.13) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Apr 2015 20:13:46 +0000 Received: from mail-qc0-f173.google.com (mail-qc0-f173.google.com [209.85.216.173]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 0DB2025793 for ; Wed, 22 Apr 2015 20:13:26 +0000 (UTC) Received: by qcyk17 with SMTP id k17so99974709qcy.1 for ; Wed, 22 Apr 2015 13:13:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=IOvp+kTCrulyvvAIcQs8IJnadW9N0BRmqYAWEP4Rhpo=; b=B5GEZmJECvHALwwFp8ur/lJQfzONJkd46ViA+qmeckFoJOFdIWu9/uik+JIXMZXb9c pjMM9gSja9dwxWZ/ryoCcYtodlZfIzKypXAjsWllnU1/AeA3os9dHFbc1VJ/3nB6ElFD jwTOJfbPzCDm6kZfLJp+7MmPEzlNxkMtsaoOEg9bVYfvvPM3b6eJg5/0rdeGDYtAB15C VBMZeq01QqvBwLaOCTX83yWMd6EYE+Bv+K2rjCrNZC3uokrFuADmhcD6IRa23vOOF3fE PeOqCWSsWJm/fPiRso7ZWMeMP+JajqbZ4LCPYn52/vm6Odz8ESPu2GAf/6+e3xJ0DuXq HYUA== X-Gm-Message-State: ALoCoQl1UiSmtrAbm9XqqJj7DBfO7IguwhmTMsA8c29qggItIHxKOnFED+BibRdOaQSWwcQTyeco X-Received: by 10.55.21.17 with SMTP id f17mr52410856qkh.41.1429733605262; Wed, 22 Apr 2015 13:13:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.84.138 with HTTP; Wed, 22 Apr 2015 13:13:05 -0700 (PDT) In-Reply-To: References: From: Sean Busbey Date: Wed, 22 Apr 2015 15:13:05 -0500 Message-ID: Subject: Re: JIRA reply threading To: dev Content-Type: multipart/alternative; boundary=001a1147f248aa605f051455cbef X-Virus-Checked: Checked by ClamAV on apache.org --001a1147f248aa605f051455cbef Content-Type: text/plain; charset=UTF-8 Not present if you aren't logged in, also existing responses not threaded if you aren't logged in, I think? Still can't stand the implementation. On Wed, Apr 22, 2015 at 3:09 PM, Andrew Purtell wrote: > Is it just me or are the 'Reply' links for threading replies on JIRA > sometimes present and sometimes not ? > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) > -- Sean --001a1147f248aa605f051455cbef--