On Tuesday 25 May 2010 12:38:34 Bill Hart wrote:
> Someone has just pointed out that the mpir.texi document, from which
> our pdf documentation is generated contains:
>
> @c @author Original version by Torbj@"orn Granlund, Swox AB - modified
> by William Hart
> @c @email{[email protected]}
>
> So, not only did we not remove the original author information, but we
> correctly added additional author information!!
>
> Now, we are looking into why this isn't appearing on the title page of
> the pdf documentation. That appears to be a technical issue! We will

note the @c before the @author , that is a comment , I assume because @author 
crashed earlier pdf makes

> also add "The GMP Development Team" as per the latest GMP
> documentation.
>
> So, next time Mr. Granlund, check your facts before posting nonsense!
>
> Bill.
>
> On 24 May, 19:58, Bill Hart <[email protected]> wrote:
> > I don't think that is something we can cover on the MPIR website.
> >
> > You might consider "Windows support", "FSF copyright assignment" and
> > other issues.... It should just be clear that GMP won't, by and large,
> > just accept our contributions. You might also consider that numerous
> > individuals *did* try to contribute their improvements to GMP.
> >
> > I agree the the fork was intimately tied up with this stuff. But
> > again, let's be positive about MPIR's current focus. I don't think we
> > need to revisit this on the website.
> >
> > Bill.
> >
> > On 24 May, 19:34, leif <[email protected]> wrote:
> > > On 24 Mai, 20:13, Bill Hart <[email protected]> wrote:
> > > > OK, I made a little bit of a change to the "about" section of the
> > > > MPIR website. It now has:
> > > >
> > > > "MPIR is an open source multiprecision integer (bignum) library
> > > > forked from the <a href="http://gmplib.org/";>GMP (GNU Multi
> > > > Precision)</a> project. It consists of much code from past GMP
> > > > releases, in combination with much original contributed code."
> > > >
> > > > I doubt that addresses the concern you had, but it is, in my opinion,
> > > > clearer and simpler than what we had. In particular I removed the bit
> > > > about originally being a fork of GMP 4.2.1 (which was LGPL v2+), etc.
> > > > I don't think that information is particularly useful or serving any
> > > > definite purpose any more, though there wasn't anything particularly
> > > > wrong with it.
> > > >
> > > > But again, I'm happy to change something if it isn't clear, or
> > > > perhaps I should say that the new MPIR webmaster will (I've just been
> > > > transferring credentials over for that).
> > >
> > > (primary goals:) "To maintain full interface support with GMP - MPIR
> > > is a drop-in replacement for GMP."
> > >
> > > So it isn't clear why MPIR forked rather than contributing their
> > > enhancements to GMP.
> > > (And one may ask himself why and when he should use MPIR instead of
> > > GMP and vice versa.)
> > >
> > > -Leif
> > >
> > > --
> > > To post to this group, send an email to [email protected]
> > > To unsubscribe from this group, send an email to
> > > [email protected] For more options, visit this
> > > group athttp://groups.google.com/group/sage-devel
> > > URL:http://www.sagemath.org
> >
> > --
> > To post to this group, send an email to [email protected]
> > To unsubscribe from this group, send an email to
> > [email protected] For more options, visit this
> > group athttp://groups.google.com/group/sage-devel
> > URL:http://www.sagemath.org

-- 
You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/mpir-devel?hl=en.

Reply via email to