Brice / Samuel --
We seem to be in pretty good shape:
- github commits work as expected
- we're getting emails sent upon pushes to github
- DongInn got the "refs #X" and "closes #X" stuff working (i.e., putting tokens
in git commit messages affects Trac tickets -- see
http://trac.edgewall.org/w
On Sep 6, 2013, at 10:50 AM, Pavan Balaji wrote:
> Aha! I was never happier to be wrong. :-) Woohoo!
>
> Thanks for the clarification.
No problem. Go smack your partner for not doing their due diligence properly.
:-)
> FWIW, I said that you guys have LGPL-2.1 code, so technically it's sti
Aha! I was never happier to be wrong. :-) Woohoo!
Thanks for the clarification.
FWIW, I said that you guys have LGPL-2.1 code, so technically it's still
correct ;-). But I blame Fortran for this oversight.
-- Pavan
On Sep 6, 2013, at 9:41 AM, Jeff Squyres (jsquyres) wrote:
> On Sep 6, 2
On Sep 6, 2013, at 10:30 AM, Pavan Balaji wrote:
> The mpich-3.0.x series was released with hwloc-1.6.x. One our of partners
> just brought it to our attention that this version of hwloc has LGPL-2.1 code
> in src/libltdl.
Because GPL violations are quite serious, I want to be totally clear:
Folks,
The mpich-3.0.x series was released with hwloc-1.6.x. One our of partners just
brought it to our attention that this version of hwloc has LGPL-2.1 code in
src/libltdl.
We are upgrading our code to use hwloc-1.7.x, which doesn't seem to have this
problem, but if 1.6.x is still supported
