Hello Miguel, Initially I used the following procedure to set the patch 1. Downloaded the lzma file and untarred it, 2. Then I did a git pull so I get the latest master 3. Then edit the necessary changes, then built it using ./sage -b and tested using ./sage -t, if everything was okay I used to commit onto the trac server.
I had this doubt on setting the repo up.For a start I forked the repo on github and have cloned the sage repo from github onto my local system, I had to run the make file, here are my doubts on this subject: 1. Is running make once enough, in sense after once I have run make can I use ./sage -b after editing the code. 2. Can I push the binary that I have untarred from the lzma onto github, work on this code and then push intermediate tickets onto the trac server. It would be great if you could comment if I am going in the right direction. Thanks. On Wed, Apr 23, 2014 at 10:31 PM, Amit Jamadagni <[email protected]>wrote: > Hello Harald, Miguel, > I would like to work on a repo and then create a ticket > on the trac server once there is sufficient amount of code in there. I > guess we can have few intermediate tickets with decent amount of code in it > rather than creating a single ticket with bulk code as it would be easy to > review. I have tried to setup the blog and here is the link > https://knotsknotted.wordpress.com/. > > > On Wed, Apr 23, 2014 at 9:27 PM, Harald Schilly > <[email protected]>wrote: > >> Hello everyone, and yes, thank you for posting this. You almost read my >> mind ;-) >> >> On Tue, Apr 22, 2014 at 12:33 PM, Miguel Angel Marco >> <[email protected]> wrote: >> > Here are some tasks that you should do: >> > >> > 1) Create a blog ... >> >> Yes, everyone has to do this. Post a short or longer status update >> once a week ... and you can start right now with a nice introduction. >> What's also important is to "tag" the postings. For example, in >> blogger, wordpress and so on you can add a label like "sage" to your >> postings. Then, there is a view of your post where only those postings >> associated with that tag "sage" are visible. >> Why? I'll add this feed of postings to Sage's community blog: >> http://planet.sagemath.org ... where your postings will appear right >> next to all the other ones. So, once you have done this, please send >> me the blog url and an info about this tag. >> >> > >> > 2) Create a repository for your code on this project. Since sage uses >> git >> > and guthub, i recommed you to use github. But if you prefear something >> else, >> > like bitbucket, it is ok. >> >> Yes, Github or a branch on Sage's trac. In case you are working on the >> Android app, forking that project is of course the preferred way. >> >> Harald >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-gsoc" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/sage-gsoc. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "sage-gsoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-gsoc. For more options, visit https://groups.google.com/d/optout.
