On 4 January 2013 11:42, P Purkayastha <ppu...@gmail.com> wrote: > > I just convert my worksheets to .sage files and put it on github. You can > link to the raw files, and you can put up specific instructions how to run > the files, etc., by writing a README file. > > If you want to do any modifications later, you can simply update the file > and then you also have a git history to keep track of your changes. > > I suppose you could also put up the sws files, but then they won't be easily > readable (partly because some OSs won't recognize them as archives). > Moreover, people might not have a sage server ready to check/import your > work. >
Thanks, I had not thought of using github for this, but then I have only recently acquired a github account (I converted both eclib and ecdata from mercurial repositories hosted on googlecode to git repositories on github, since everyone else seems to be moving in that direction, and why would I not want to learn how tu use a 5th version control system anyway?). A disadvantage is that one loses all the beauty of a workable worksheet which can be instructive to look at even if one does not want to run the code. John > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To post to this group, send email to sage-devel@googlegroups.com. > To unsubscribe from this group, send email to > sage-devel+unsubscr...@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel?hl=en. > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
