Thanks Alex. Sorry it is going to take me a while to get to this. We are insanely busy at this time of year.
Yes, the manual can link to your wiki, so long as you consider that a permanent URL. Bill. On 16 June 2016 at 20:53, Alex Dyachenko <adya...@gmail.com> wrote: > Just pushed the documentation update. The new chapter is similar to and > follows the C++ Class Interface chapter, but came out to about twice its > length, 19 pages. Can't blame it there, it's essentially an overview of > all of MPIR's functions. Should the manual link to the URL of the > browsable version of the documentation (hosted in my fork's wiki)? > > On Mon, Mar 28, 2016 at 10:14 AM, 'Bill Hart' via mpir-devel < > mpir-devel@googlegroups.com> wrote: > >> Hi Alex, >> >> Thanks for doing this. >> >> If there is a lot of documentation then I would prefer a separate >> document. By all means add a note in the main documentation explaining >> where to find the full documentation. >> >> The reason for separating it like this is just for convenience of the >> user. They won't have to go looking through the manual to find what they >> are looking for. >> >> Bill. >> >> On 28 March 2016 at 16:00, Alex Dyachenko <adya...@gmail.com> wrote: >> >>> I have moved all the gmp-h.in changes to gmp-impl.h instead. gmp-h.in >>> now stands unchanged, and I have added comments to the additions in >>> gmp-impl.h, as well as in the out_raw.c and inp_raw.c sources to explain >>> what was changed and why. Sorry, with the size of the pull request the >>> diffs in these last two are not shown on github. >>> >>> Now if I could just finish the documentation... Have you decided if you >>> would like a chapter in the MPIR manual or a separate document? >>> >>> Alex >>> >>> On Mon, Jan 18, 2016 at 11:50 AM, Alex Dyachenko <adya...@gmail.com> >>> wrote: >>> >>>> I have rearranged the project files as discussed. >>>> >>>> Thanks for the positive feedback! >>>> Alex >>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "mpir-devel" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/mpir-devel/WwzswnAMKSk/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> mpir-devel+unsubscr...@googlegroups.com. >>>> To post to this group, send email to mpir-devel@googlegroups.com. >>>> Visit this group at https://groups.google.com/group/mpir-devel. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "mpir-devel" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/mpir-devel/WwzswnAMKSk/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> mpir-devel+unsubscr...@googlegroups.com. >> To post to this group, send email to mpir-devel@googlegroups.com. >> Visit this group at https://groups.google.com/group/mpir-devel. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to mpir-devel+unsubscr...@googlegroups.com. > > To post to this group, send email to mpir-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/mpir-devel. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at https://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
