On Wed, Apr 23, 2014 at 4:06 PM, Kannappan Sampath <kntri...@gmail.com>wrote:
> Thank you all for suggesting that I take a look at GIT. I think I feel > better now. But, still I have gotten some questions. I am trying to review > 16091. > > I have checked out the ncohen's 16091 branch and have it as a local > branch. I would like to now let sage now that there has been a change in > its code due to this branch. I assume this means I run sage -b. Is this > correct? > ​Nearly, it tells the Sage build system to check all files, and rebuild the system if necessary. Since the branch in 16091 is based on version 6.2.beta6 of the system, any changes to the branch you upload will too, if you don't merge the newest developer branch. This may work or not, depending on if the developer branch changed things near the code that you are working on (you will see this when merging). Note it's required practice that, if you upload something, it must be includable without conflict, and it must build the system and the documentation without errors, as well as not produce any doctest errors. This can only be ensured if you work with the newest developer branch. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
