> git diff ^master > > should be equivalent to > > sage -dev diff --base master
I don't know much about the plan for "sage -dev", but I generally think, it's a bad idea to maintain two interfaces for the same task. Why should git-savvy people learn the "sage -dev"-way? Why waste time documenting the "sage -dev" way? Git is a collection of scripts, so it would equally well be possible to provide git related things through calling git. For example, I've written a script git-snapshot which commits all files in the current directory to a branch called "snapshot" but does otherwise not change anything. That script lies under $HOME/bin, i.e. is in my PATH and thus I can easily call it via git snapshot just as any other command. Just my 2 cents. Ralf -- 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.
