You probably want
sage -dev checkout --branch master
I, too, implemented the --ticket / --branch switches in the git trac
subcommand, but am more and more convinced that it is a huge annoyance. It
should just work without having to specify whether the input is a ticket or
a branch, that is almost always unambiguous. In other words: DWIM (Do What
I Mean), in other words. Also one of the git development tenets.
"sage -dev vanilla" is probably another way to do the same thing. Since we
always want at least two equivalent ways to do the same action, right?
</irony>
On Tuesday, December 17, 2013 9:30:58 AM UTC, John Cremona wrote:
>
> I was trying to follow exactly the instruction in the new (draft)
> development guide as at http://sagemath.github.io/git-developer-guide/
> since obviously what is written there must work. Here are a couple of
> things I discovered.
>
> 1. My EDITOR environment variable is always set to "emacs -nw" since I
> use emacs and don't want to wait for a full X-window to open when I am
> connected remotely. This does not work with sage --dev coment: it
> raises an error.
>
> 1'. From home I reset EDITOR to "emacs" and tried again. I was
> running a shell in a tmux window on a server at the university to
> which I had logged in from home and recommented to the tmux session.
> Nothing happened -- no editor window, and no new prompt, I had to kill
> it with Ctrl-C. And when I woke up my office desktop this morning
> there was the emacs window patiently waiting.....
>
> I am not suggesting that the dev scripts need do anything about 1'
> since it has nothing to do with Sage, just me getting my DISPLAY etc
> misconfigured. But if something can go wrong for people in future,
> the sooner we see possible problems the better. I definitely think
> that 1 should be fixed (though of course meanwhile I can enter
> comments on trac as usual).
>
> 2. the dev. guide explains how to checkout a new ticket branch in
> order to do a review. It does not say how to end this process! Of
> course "git checkout master" works, but these instructions are trying
> to make it possible for developers to never have to type "git". And I
> tried some variations on "./sage --dev checkout master" but they did
> not work (error messages about numbers of arguments).
>
> 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.
