>
>
> Really that is Travis' fault for doing an unnecessary merge. Which, in 
> turn, forced you to recompile to follow the merge.
>

   So instead I have to let my Sage recompile just because I want to work 
on a ticket not currently based on the latest development? In fact, I'm 
worried I might not even be able to start Sage because of more recent 
spkgs. If that's what I have to do, then I'm never going to review someone 
else's ticket I don't know if they mind merges to latest develop. (However 
I do take responsibility for not explicitly mentioning that I merged the 
latest develop.)

   Merging with the latest develop branch is not unnecessary as it is 
something that must be done and it would put my Sage development into a 
standstill as I almost always need the latest develop. IMO unnecessary 
merges are those where *small* unrelated changes are made to a base branch 
and merged in 1 by 1. I'm more than willing to spend time and energy to 
teach people git usage to reduce large re-compilations.

Travis

-- 
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to