On Tue, Apr 22, 2014 at 8:07 PM, Kannappan Sampath <kntri...@gmail.com> wrote: > I also need more git hand holding: I am trying to attach some code from my > local branch to a ticket. I did the following: > > Apples-MacBook-Pro:combinat apple$ sage -dev checkout --ticket 16211 > On ticket #16211 with associated local branch "ticket/16211". > > # Use "sage --dev merge" to include another ticket/branch. > # Use "sage --dev commit" to save changes into a new commit. > > Now, I tried to push by sage -dev push and the whole thing fails miserably! > :-( > > I would be very grateful for any help about how I would go about this... Also, > in the older days, when I made changes to the source code, to get SAGE to > know about it, I used to commit and build. Now, that is not sufficient? How > do I get SAGE to know the changes I have made. > > With Sincere Regards. > Kannappan
My personal opinion is that it is bet to learn the basics of git (about 3 hours), say from a book like [1]. Then use the approach to Sage development described in the badly-named section "Git the Hard Way" of [2]. Recently Volker modified the Sage dev guide (for the next release) to emphasize this approach, which I very strongly agree with. It might help you. [1] http://git-scm.com/book [2] http://www.sagemath.org/doc/developer/manual_git.html -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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.
