No need I think. Let's just merge everything we have in the experimental branch.

2009/2/17  <ja...@njkfrudils.plus.com>:
>
> On Tuesday 17 February 2009 08:42:18 Cactus wrote:
>> On Feb 15, 8:29 pm, Bill Hart <goodwillh...@googlemail.com> wrote:
>> > Lest there be any confusion, MPIR version 0.9.0 has been released. It
>> > is available from the MPIR website:
>> >
>> > http://www.mpir.org/
>> >
>> > Note that next to the download link is a link to a list of changes we
>> > have made in this release.
>> >
>> > ---------
>> >
>> > The release represents revision 1601 of the trunk directory in our
>> > subversion repository, available by anonymous access here:
>> >
>> > http://modular.math.jmu.edu/svn/mpir
>> >
>> > Development of MPIR will continue in trunk and revision 1601 will
>> > become an mpir-0.9 directory in svn. Any bug fixes to MPIR 0.9.0 will
>> > be made to *both* trunk and the mpir-0.9 branch and a service release
>> > MPIR 0.9.1 will be released.
>> >
>> > The next major revision of MPIR will be 1.0.0, due out in a few weeks.
>> > The release schedule depends on the number of developers and their
>> > activity, but the plan is to have pretty regular releases of MPIR (at
>> > least every three months).
>> >
>> > Bill.
>>
>> Hi Guys
>>
>> I am not a very knowledgeable user of SVN - how does this work?
>>
>> Does the experimental branch become the trunk?
>>
>> Or do I have to move the Windows stuff across?
>>
>> Or what?
>>
>>     Brian
>>
>
> Were we going to do a release before the k8-branch merge , ie as it is now
> r1612 , with the gmp/mpir name change only ?
>
>
> >
>

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

Reply via email to