Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <20050302154404.78493.qmail@web81610.mail.yahoo.com>
Date: Wed, 2 Mar 2005 07:44:04 -0800 (PST)
From: Jeff Levitt <derby@mylevita.com>
Subject: Re: [jira] Commented: (DERBY-102) can not insert more than 32270
 charakters in long varchar, clob
To: Derby Development <derby-dev@db.apache.org>
In-Reply-To: <4225DC74.2040403@debrunners.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

--- Daniel John Debrunner <djd@debrunners.com> wrote:

> Brenda Reyes (JIRA) wrote:
> >      [
>
http://issues.apache.org/jira/browse/DERBY-102?page=comments#action_59997
> ]
> >      
> > Brenda Reyes commented on DERBY-102:
> > ------------------------------------
> > 
> > I fixed this in the contributed DITA source files
> for the Derby Reference Manual and gave the changed
> file to Jeff Levitt, who is currently working on the
> DITA files as well.  I wanted to avoid overiding his
> changes.  I ran this change by Sunitha, and she says
> it looks good, so once the Manual is sent to Jean
> again by Jeff, please check and close this bug if
> everything looks good!
> 
> Is there any reason changes to the DITA files should
> not be handled the
> same way as code changes, through patches on the
> list? Jeff may not be
> the only person working on the DITA files.
> 
> Since no-one can see what you actually changed it's
> hard to see if your
> change is correct.
> 
> Dan.
> 
> 

I agree.  I am almost done converting the Tools and
Utilities Guide to DITA (will be done this week), and
then all the manuals will be in DITA.  I think at that
point we should remove the zips from the manuals page
and have them checked in as if they were code.  Can we
do that?