Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates
 209.85.160.41 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=WFDcABoa/xyuFmvHKCcEbAe/mhI1p++MJY4EpZ9UNabgaADpB2RMMHOPepiGVlJwkz
         3YfaE44NPnLL1CzSvs/uoNWPNdAAKUuVO2t3bz3QD/jK5/QAMqdvdDLKV/kWeJz3Aek1
         GWrFlHd4kOoeXjzG1bcUEibVICEoPHIEAAiAI=
MIME-Version: 1.0
Date: Sat, 25 Jun 2011 03:21:18 -0700
Message-ID: <BANLkTi=m6zB_c8j-0MD3aR9FOt3+j8ZpCQ@mail.gmail.com>
Subject: Re: editing JIRA comments
From: Ted Yu <yuzhihong@gmail.com>
To: dev@hbase.apache.org, apurtell@apache.org
Content-Type: multipart/alternative; boundary=bcaec5215d7bd0f19d04a686ada5

--bcaec5215d7bd0f19d04a686ada5
Content-Type: text/plain; charset=ISO-8859-1

One side note, I reserve my right to edit JIRA comments / contents if the
comments or contents of the JIRA reveal my company (or other company)'s IP.

Aaron has done a good job of presenting redacted log in his JIRA. But
sometimes people were in a hurry.

I hope the above is a legitimate exception to the general rule.

Thanks

On Fri, Jun 24, 2011 at 3:11 PM, Ted Yu <yuzhihong@gmail.com> wrote:

> I will refrain from doing this again.
>
>
> On Fri, Jun 24, 2011 at 3:07 PM, Andrew Purtell <apurtell@apache.org>wrote:
>
>> -1 on allowing edits of issue comments.
>>
>> We had this feature disabled on the HBase project for a while but
>> obviously it is allowed again.
>>
>> Issues are external memory of a project. If they are volatile, that memory
>> is volatile, which I find unacceptable, if the record can be selectively or
>> conveniently edited.
>>
>>   - Andy
>>
>> > Subject: [jira] [Issue Comment Edited] (HBASE-451) Remove
>> HTableDescriptor from HRegionInfo
>>
>>
>

--bcaec5215d7bd0f19d04a686ada5--