On Tuesday, December 17, 2013 3:59:42 PM UTC, John Cremona wrote: > > That is a good point. But what a pity. It might make it impossible > for a branch to be properly tested and given a positive review!
You can merge with the current master and then build the ticket to check that it still builds. There is no point in checking in the merge as the release manage will have to merge the ticket either way, the extra merge just clutters the history. Review mostly means reading the code and check that it is of good quality. Of course that includes running it and verifying that it produces the desired result. But checking that it still works with the most recent version is IMHO better done by the computer, that is what the patchbot / buildbot are good for. development? How can I continue to work on a branch after pushing it > to a trac ticket, if I am not allowed to make changes that might > affect anyone who has branched off of that? > You can (and are encouraged to) keep working on it, just add more commits. Git is a system to join the resulting directed-acyclic graph of commits back into a consistent source tree. -- 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.
