Mailing-List: contact user-help@beehive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Beehive Users" <user@beehive.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of richfeit@gmail.com designates
 64.233.162.195 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:x-enigmail-supports:content-type:content-transfer-encoding;
        b=myYq3eh3M6poLLs4jTOIZEoD0R26AU/KV3QZ3HbN7TDEqYSTo3Jw5ybOFef/k4izvmEjW71stuBXXX6keUkLO5JugZORvfTbfkAm+80Atu3bBnspwy612UnM9Ap4OeG+MTwYPzKTVFggsyJfcENpy991PvhkAK4G4rEwvjgeEcU=
Message-ID: <431D475E.6020900@gmail.com>
Date: Tue, 06 Sep 2005 01:38:06 -0600
From: Rich Feit <richfeit@gmail.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: Beehive Users <user@beehive.apache.org>
CC: mail@adamjenkins.net
Subject: Re: BEEHIVE-843 status?
References: <1125811088.25317.3.camel@main.adamjenkins.net>
 <ba6911de050905214660843590@mail.gmail.com>
In-Reply-To: <ba6911de050905214660843590@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

FYI, I think that your patch could go in first, then be refactored for 
code sharing (if that turns out to be a possibility).  So hopefully it 
goes in immediately after we branch.
Rich

Carlin Rogers wrote:

>Hi Adam,
>
>I didn't notice a patch for BEEHIVE-843. Are you thinking of 863? If so, the 
>implementation of BEEHIVE-863 is really a new feature and would most likely 
>get checked into the main trunk by a committer after the branch for the V1 
>release. You should also note that the patch for 863 will probably need some 
>modifications as far as the JavaScript goes and looking at possible reuse of 
>some JavaScript used in datagrid. If it's not 863 you're talking about, I do 
>know there are a couple of other small patches for bugs that will also be 
>committed after the branch. Most of the changes being committed now are for 
>doc, etc. 
>
>Kind regards,
>Carlin
>
>
>On 9/3/05, Adam Jenkins <mail@adamjenkins.net> wrote:
>  
>
>>Hi All,
>>
>>What's the status of jira issue BEEHIVE-843 ... there seems to be a
>>patch submitted but no comments after that. Has it made it into beehive
>>yet (I have some code that would benefit from the issue fix).
>>
>>Cheers
>>Adam
>>
>>
>>    
>>
>
>  
>