>
> Has anyone tried it? Getting rid of "I checked out that branch, and it
> triggered a 10-minute Sage rebuild" things would be great...
>
At some point I will get tired of repeating it, but there is absolutely no
reason on earth why loading a branch should trigger *any* kind of rebuild
except the files that were changed.
Checkout the latest develop that you have and create a new branch there
with:
git checkout -b tmp develop
Then you pull the distant branch:
git pull trac <branch name>
Then 'sage -b' and you are done.
I have a short bash script that does that very easily, loads the branch
from the ticket number, and if necessary adds a meaningful commit message
("Merged with beta<whatever>") on the merge commit.
So --> there is never any reason to recompile anything short of a new beta,
or the files that a branch changed.
Nathann
--
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
