[sage-devel] Re: documentation bug: git-trac instructions don't mention git commit

2015-05-28 Thread kcrisman
> > I won't recommend '-a'. Explicit addition of files using 'git add' is > safer as to you do not accidentally push too much upstream... > > I 100% agree, esp. since sometimes there are extra changes lying around - one of the few places I like git better than Mercurial. I think I mentioned so

[sage-devel] Re: documentation bug: git-trac instructions don't mention git commit

2015-05-28 Thread Dima Pasechnik
On Monday, 25 May 2015 23:22:03 UTC+1, Ursula Whitcher wrote: > > 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

[sage-devel] Re: documentation bug: git-trac instructions don't mention git commit

2015-05-25 Thread Volker Braun
The preceeding section explains how to make local edits and commit them (see http://doc.sagemath.org/html/en/developer/walk_through.html#commits-snapshots). The only thing that the "git-trac section" adds is how to exchange commits over the internet. This is why there is no special mention of h