Once I have successfully navigated this process, I would happily provide feedback on the documentation. (Thanks for your tolerance with my questions!)
On Friday, June 5, 2015 at 7:15:39 PM UTC+1, kcrisman wrote: > > I have just made a *lot* of revisions to the files in the sage/sandpiles/ >> directory and would like to post then to the trac system to be reviewed and >> included in a future version of sage. I have followed the instructions >> on the "collaborative development with git-trac" page ( >> http://doc.sagemath.org/html/en/developer/git_trac.html) up to and >> including the point of opening a new ticket. My question is: what, in >> detail, are the next steps? (Do I go back to the documentation on setting >> up Git at this point, creating a clone of github.com/sagemath/sage.git? >> Is there anyway of getting around making a local version of sage, i.e., can >> I download a binary and work from that? >> > > Maybe, though it may not build properly. > > >> Does git-trac then interact with this clone somehow?) I don't have >> much experience with git and could really use help in the form of explicit >> step-by-step instructions (and it would be nice if the Sage documentation >> had spelled out these steps, too). >> >> > PLEASE tell us ways to make the doc better. The people who mostly wrote > it know git backwards and forwards, so the fact that someone very smart > can't just do it immediately tells me that I am right that it isn't just > zombies who can't figure it out, which I have been trying to say all along. > > http://doc.sagemath.org/html/en/developer/git_trac.html#chapter-git-trac > http://doc.sagemath.org/html/en/developer/walk_through.html#branching-out > > In your specific case, if you already have a Sage copy with changes, and > you haven't done any git commits, you could conceivably do something like > > git checkout -b my_branch > > (someone will tell me if my syntax is wrong, but I think it will create a > new branch and take all the changes you made along with you) and then > 'push' that. > > You presumably shouldn't have to clone, I *think* every Sage copy comes > with a git repo at this point - is that correct, all? > -- 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.
