Re: ant git commit: Check spelling

Point taken. Apologies for comments that could be considered lousy or snarky. Any opinions on code quality checks (Checkstyle/JaCoCo/SpotBugs/Simian etc) in nightlies and doing something to improve their scores? Gintas On Thu, 13 Sep 2018 at 15:00, Nicolas Lalevée wrote: > > > [1] https://gith

Re: ant git commit: Check spelling

> [1] https://github.com/apache/ant/pull/66/files > [2] > https://github.com/apache/ant/commit/54b6df2f44c5cb4f9573f99330c2d2908f1bf506 > At the *first* line of the diff presented on github, I can tell the commit is

Re: ant git commit: Check spelling

After all the numerous mail discussions that we have gone through over this last year about commits like these, are you seriously asking what's the difference between [1] and [2]? It's attitude and questions like this that makes me wonder if you are willingly trolling the project or if I have compl

Re: ant git commit: Check spelling

How was this different from PR #66? Gintas On Tue, 11 Sep 2018 at 06:55, Jaikiran Pai wrote: > Things haven't changed (nor do I expect any changes anymore). To say the > least - it's followed the same pattern: > > - do changes like these > > - when requested not to do such changes, argue over i

Re: ant git commit: Check spelling

Things haven't changed (nor do I expect any changes anymore). To say the least - it's followed the same pattern: - do changes like these - when requested not to do such changes, argue over it and move it to some abstract discussion - then give an impression it won't be repeated - few days down

Re: ant git commit: Check spelling

I have been away from the project out of boredom. Still curious, I came to read some emails. It seems things didn’t changed much: yet another unreadable commit with a log which doesn’t indicate what it actually do. > Le 9 sept. 2018 à 09:09, gin...@apache.org a écrit : > > Repository: ant > Up