On 21 December 2013 15:45, Travis Scrimshaw <tsc...@ucdavis.edu> wrote: > Works for me now. Thank you Andrew. > > > John, > Since it's been pushed to trac, all you need to do is manually set the > "branch" field with the name of the branch (which you can see by running > "git branch" [or sage -git branch if you don't have git installed] anywhere > in the sage folder).
The branch field was already set and still is (see http://trac.sagemath.org/ticket/15554), which is why I was little puzzled by Volker's comment. If you or someone could actually verify that that ticket is in a state ready for reviewing, that would be helpful. Comparing with my other recent one at #15556, there is a difference: both the Branch and Commit field are filled in but after the branch name there is no "Commits" link. John > > Best, > Travis > > -- > 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/groups/opt_out. -- 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/groups/opt_out.
