Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Date: Mon, 30 Aug 2010 12:09:10 +0200
From: Gilles Sadowski <gilles@harfang.homelinux.org>
To: dev@commons.apache.org
Subject: [Math] Large commit pending
Message-ID: <20100830100909.GK17370@dusk.harfang.homelinux.org>
Mail-Followup-To: dev@commons.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
X-DCC-scarlet.be-Metrics: sif 20001; Body=1 Fuz1=1 Fuz2=1
X-Virus-Checked: Checked by ClamAV on apache.org

Hello.

I have a rather large batch of changes to commit after working on the
following issues:
 MATH-394
 MATH-397
 MATH-404

Not everything is fixed yet, and other possible problems have been detected.
I'll create a new "unified" JIRA issue to report everything that should be
examined as a result of this commit.

The pending commit affects pretty much all files in package "optimization".
[The removing of code duplicates necessitated moving some functionality up
the class hierarchy, which involved changes in existing interfaces and
creation of new ones, which then implied a wave of modifications in affected
files.]
Despite some important work left to be done, I'd rather not further delay the
commit since I already had some conflicts following the changes due to the
addition of "FastMath". [I hope that I did correct everything properly.]

So, please tell me whether I can go ahead with the commit, or let me know if
people need to modify any file in package "optimization" and wish to have
the opportunity to do it before my commit.


Gilles

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org