Hello everybody ! On 16 November 2014 01:48, john_perry_usm <john.pe...@usm.edu> wrote: > > (1) When switching development to Git, it became harder for the less > talented to contribute. I'm not the only one who encountered a complete > recompilation of Sage when reviewing a new ticket -- even one that didn't > touch Cython. See, e.g., some of my comments on ticket #17298, where at one > point I wrote, "I can't afford to tie up my installation for 2 hours of > compilation every time a few lines of Python code change." > > This used not to occur in Mercurial.
Just wondered if we could not have some "git hook" (I do not exactly know what it can do) to make sure that one cannot checkout a branch which is not a descendent of the latest release of Sage in the local history. Thing is that to my experience this is the only reason why git triggers big recompilations. So what having a git hook saying something like "you cannot checkout this branch, it is too old. If you want to use it, merge it with the latest beta instead" ? And we could have some "-f" flag when we really want to do that... But that would prevent newcomers from wasting a couple of hours. 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
