On Thu, 6 Oct 2016 10:36:11 -0700, Gary Gregory wrote:
On Thu, Oct 6, 2016 at 10:07 AM, Dave Brosius
wrote:
I'd vote for putting down the paint brushes temporarily and consider
the
bike shed done.
Let's get 1.0 out, and then folks can work on 1.1 while getting
feedback
from users, etc.
On Sun, 9 Oct 2016 20:07:21 -0400, Rob Tompkins wrote:
I'm indifferent on the documentation here. But, I figure the changes
should be in there either way.
Sure.
If we think it better to have two jiras
to sufficiently document the change, I'll back it out, make just the
.travis.yml change and
On Mon, 10 Oct 2016 01:51:37 +0200, Emmanuel Bourg wrote:
Le 10/10/2016 à 01:40, Gilles a écrit :
For months, Travis consistently did not work (i.e. even when
that non-deterministic passed, which it does 99% of the time
for truly uniform RNG) even though local and Jenkins builds
went fine.
The
I'm indifferent on the documentation here. But, I figure the changes should be
in there either way. If we think it better to have two jiras to sufficiently
document the change, I'll back it out, make just the .travis.yml change and
open a separate jira for the RetryRunner.
Just let me know wha
Le 10/10/2016 à 01:40, Gilles a écrit :
> For months, Travis consistently did not work (i.e. even when
> that non-deterministic passed, which it does 99% of the time
> for truly uniform RNG) even though local and Jenkins builds
> went fine.
>
> The problem reported as MATH-1387 was about what was
On Mon, 10 Oct 2016 01:26:15 +0200, Emmanuel Bourg wrote:
Le 10/10/2016 à 01:21, Gilles a écrit :
The first sentence of that comment was:
"The latter is not related to either Travis or the JVM version."
Whereas MATH-1387 is entitled:
"Travis CI does not work in master branch"
For Travis t
Le 10/10/2016 à 01:21, Gilles a écrit :
> The first sentence of that comment was:
> "The latter is not related to either Travis or the JVM version."
>
> Whereas MATH-1387 is entitled:
> "Travis CI does not work in master branch"
For Travis to work the tests have to pass. That's why the build
On Mon, 10 Oct 2016 01:12:05 +0200, Emmanuel Bourg wrote:
Le 10/10/2016 à 00:59, Gilles a écrit :
How is this change related to MATH-1387 ?
In MATH-1387 you suggested: "Sometimes the sequence is not uniform
enough according to the statistics criterion. Just run the build
again",
that's what
Le 10/10/2016 à 00:59, Gilles a écrit :
> How is this change related to MATH-1387 ?
In MATH-1387 you suggested: "Sometimes the sequence is not uniform
enough according to the statistics criterion. Just run the build again",
that's what this commit clearly does: it runs the failed test again.
Emm
On Sun, 09 Oct 2016 20:36:44 -, chtom...@apache.org wrote:
MATH-1387: adding RetryRunner to
RandomUtilsDataGeneratorJDKSecureRandomTest
How is this change related to MATH-1387 ?
Gilles
Project: http://git-wip-us.apache.org/repos/asf/commons-math/repo
Commit:
http://git-wip-us.apache.o
>
> With all of the change above, my question would be "Why?". What are the
> benefits of the proposed changes? What are the impacts on the other
> supported operating systems?
>
Originally, I was surprised by the use of MSVC as main toolchain for
Windows, then I've planned to allow Apache Daemon
Am 09.10.2016 um 17:50 schrieb Matt Sicker:
> You can do a git rebase on the release branch to get master back in, though
> if you've already run the version update stuff on it, I'm not completely
> sure how that works (though it should work out just fine).
I would also go for the rebase approac
You can do a git rebase on the release branch to get master back in, though
if you've already run the version update stuff on it, I'm not completely
sure how that works (though it should work out just fine).
On 9 October 2016 at 06:37, Benedikt Ritter wrote:
> Hello Oliver,
>
> Oliver Heger sch
It looks as though the byte[] arrays are often converted into a
ByteArrayInputStream.
If not, then the other common use-case is an indexed read.
Encapsulating the byte[] data in a class that gives access to these
might be a solution.
Likewise for int[] and other data.
On 6 September 2016 at 07:47
A few days ago a .gitattributes was applied, but it is causing some wierdnesss
in the resources and a few other files.
The following files are "modified" on clone:
src/main/java/org/apache/commons/io/serialization/package.html
src/site/xdoc/upgradeto2_3.xml
src/test/resources/org/apache/commons/
GitHub user pdinc-oss opened a pull request:
https://github.com/apache/commons-io/pull/24
[IO-516] fixed line endings for source files and ignored line endingsâ¦
CLA on file
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pdinc-o
Hello again,
sebb schrieb am So., 9. Okt. 2016 um 13:53 Uhr:
> On 9 October 2016 at 12:46, Benedikt Ritter wrote:
> > Hello,
> >
> > schrieb am So., 9. Okt. 2016 um 12:46 Uhr:
> >
> >> Author: sebb
> >> Date: Sun Oct 9 10:46:51 2016
> >> New Revision: 1763958
> >>
> >> URL: http://svn.apache.
On 9 October 2016 at 12:53, sebb wrote:
> On 9 October 2016 at 12:46, Benedikt Ritter wrote:
>> Hello,
>>
>> schrieb am So., 9. Okt. 2016 um 12:46 Uhr:
>>
>>> Author: sebb
>>> Date: Sun Oct 9 10:46:51 2016
>>> New Revision: 1763958
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1763958&view=rev
On 9 October 2016 at 12:46, Benedikt Ritter wrote:
> Hello,
>
> schrieb am So., 9. Okt. 2016 um 12:46 Uhr:
>
>> Author: sebb
>> Date: Sun Oct 9 10:46:51 2016
>> New Revision: 1763958
>>
>> URL: http://svn.apache.org/viewvc?rev=1763958&view=rev
>> Log:
>> Simplify code and avoid exposing mutable
On 9 October 2016 at 12:47, Benedikt Ritter wrote:
> Hello,
>
> schrieb am Fr., 7. Okt. 2016 um 12:04 Uhr:
>
>> Author: sebb
>> Date: Fri Oct 7 10:04:06 2016
>> New Revision: 1763721
>>
>> URL: http://svn.apache.org/viewvc?rev=1763721&view=rev
>> Log:
>> Unused
>>
>> Modified:
>>
>> commons/prop
Hello,
schrieb am Fr., 7. Okt. 2016 um 12:04 Uhr:
> Author: sebb
> Date: Fri Oct 7 10:04:06 2016
> New Revision: 1763721
>
> URL: http://svn.apache.org/viewvc?rev=1763721&view=rev
> Log:
> Unused
>
> Modified:
>
> commons/proper/imaging/trunk/src/main/java/org/apache/commons/imaging/formats/jpe
Hello,
schrieb am So., 9. Okt. 2016 um 12:46 Uhr:
> Author: sebb
> Date: Sun Oct 9 10:46:51 2016
> New Revision: 1763958
>
> URL: http://svn.apache.org/viewvc?rev=1763958&view=rev
> Log:
> Simplify code and avoid exposing mutable array unnecessarily
>
> Modified:
>
> commons/proper/imaging/trun
Hello Oliver,
Oliver Heger schrieb am Sa., 8. Okt. 2016 um
16:50 Uhr:
> Hi,
>
> for LANG-1275 which I have just created I already have a fix that I
> could directly commit. Is it okay to do this or would this interfere
> with the preparations for the 3.5 release?
>
Sorry for the late reply. I'm
23 matches
Mail list logo
