I found a documentation "bug": literally following the instructions for 
ticket creation and updates at 
http://doc.sagemath.org/html/en/developer/git_trac.html results in the 
publication of empty tickets, because there's no mention of *committing* 
changes.  This is now ticket 18504:

http://trac.sagemath.org/ticket/18504

If I were to fix these instructions, I would add something along the lines 
of, "Now, edit some files.  You can save the changes you have made by 
typing 'git commit -a' and recording a commit message.  Your commit message 
should be a short summary of what you have done, featuring an evocative 
verb."  However, I am by no means a git expert.  Are there other important 
commands we should recommend here?

--Ursula.

-- 
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.

Reply via email to