On Thursday 03 September 2009 21:58:02 Jason Moxham wrote: > On Wednesday 02 September 2009 20:08:48 Bill Hart wrote: > > Hi all, > > I finally managed to work out how to set up a Git repo on my new machine > > and publish it to the web: > > > > http://selmer.warwick.ac.uk/gitweb/FLINT-Lite.git > > > > This is for my new FLINT-Lite project, but at this point much of the code > > in there may be useful to MPIR, it contains a module called ulong_extras > > which deals with single limb arithmetic. > > We could do with a proper set of functions/macros for single(and double) > limb operations , and expose them to the user. I have quite often used mpz > types not because they are bignum's but because I then have gcd,sqrt, etc > allready done. > > > If anyone is interested in that project, there is a google group which I > > just started: > > I certainly interested in the single limb stuff , nice lot of highly > optimized asm code to write , just what I like , dont know where the time > is going to come from :( > > > http://groups.google.co.uk/group/flint-devel?hl=en > > > > If you just want to play around with git, there's some basic instructions > > on the first post to that list. But feel free to post questions here. > > Once I get a bit more familiar with gitweb I'll make a repo of MPIR from > > our current svn repo and post it on that same website. It should be no > > problems to give people write access to it, though it isn't 100% > > necessary with git, you can just publish your repo and we can pull from > > it. > > > > If you want to play right away: > > > > git clone git://selmer.warwick.ac.uk/FLINT-Lite.git FLINT-Lite > > > > (make check does something if it knows where MPIR is). > > > > It would be great to have a similar project for MPIR, i.e. x86_64 only, > > just drop files in and no makefile or configuration nonsense, etc. It > > might be worth thinking about an MPIR-Lite which is really, really easy > > for people to contribute to. What do people think of that idea? Most of > > the code could then be "ported" or modified to the standard MPIR style > > and pulled into the main MPIR project, but the average contributor > > wouldn't have to understand all the intricacies of MPIR development to > > contribute! > > > > Bill. > > Sound good , do we need to do a MPIR-lite though? How about just putting it > in the "demo" directory. We could rename the directory mpir-ext or > future-code , and have a gmp-impl.h and longlong.h in there.We could build > a libmpirext.a from it , or just a standalone exe > > Another very important point , is that new contributers can see their code going in , and being used. The Sage project makes a point of this , and I fully agree with it.
I've just checked some dates , because I didn't want to rely on memory as I may of exaggerated it in my mind, but I contributed some code to a project a few years back , and it didn't appear until the next release which was 3.5 years later :( , what a joke. Jason --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
