git diff ^master should be equivalent to
sage -dev diff --base master Make sure that your master branch is up-to date by pulling from the git repo first. If the above has too much stuff then it is pretty clear that you haven't updated master. It is a fundamental goal of git to be able to develop without having a network connection, and a side-effect of that is that changes in the remote repo are only available after you download them. On Tuesday, December 17, 2013 12:08:32 PM UTC, John Cremona wrote: > > I successfully checked out ticket #8723 and ran "make". In order to > review the changes I need to know what the changes are on this ticket. > As I discovered elsewhere, the instruction in the developer's guide > to give the command "./sage -dev diff" does not work as suggested > there, it gives 0 output, and what instead you have to do is ./sage > -dev diff --base master. Well, I just did tat and the output is 38137 > lines long. That's right, nearly forty thousand lines. > > I tried using git log to give a git hash instead of the branch name > "master" but all that I tried gave the error message that the has was > not a valid branch on the remote system. But using plain git I could > do > > git diff 0c6fcdf462e329c80eeaf2841ac1659308 > > having guessed from git log that this hash was a reasonable place to > start from, and that did give a sensible output, as did > > git diff HEAD^ > > and similar. But to review a ticket we need to know how far back to > go in this, and how do we do that? > > I am tempted to kill this branch, and do some real work, and get back > to Sage development when it is easier to use. I do realise that > several people have spent hundreds of hours on this over the last > year, but the system is not yet ready for use by others, it seems. > But surely we need more people to try out the new system -- other than > the ones who wrote the new system -- and give feedback, which is what > I have been trying to do. So I will remain optimistic and hope that > my comments will be taken as a constructive contribution, which is how > they are intended! > > John > -- You received this message because you are subscribed to the Google Groups "sage-git" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
