> We are probably ready to merge the MPIR-EXP branch into trunk but this
> will mean that there will be a (hopefully) short period during which the
> trunk won't build correctly.
> To minimise this period, it will be necessary to coordinate changes to the
> source code and to Windows Visual Studio build, the Windows command line
> build and the *nix/GCC builds.
> There are quite a large number of new C files involved and many new tests
> for the new FFT. I can provide information about the differences between
> the trunk and the MPIR-EXP branch if this will help in making these
> changes.
> I assume that Jason will need to look at the Windows command line build
> after the merge. Are you in a position to update this build if I now do
> this merge, Jason? Or is it likely to pick up the changes without any
> manual action on your part?
Brian
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mpir-devel/-/dc-tkjET1dIJ.
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.
