>From Dan Bump:
Hi Anne, I'm not cc:ing the google group since I don't think I'm authorized to post from this email address. But I'm cc:ing Andrew and Travis. I am in Davis now. Greg Musicker was arriving on the shuttle as I got back from dinner. Here is a link to my slides: http://sporadic.stanford.edu/bump/Gittalk.pdf > - Should we use a fork for sage-combinat? Or branches for the various patches > or projects? It seems to me that a fork would be a bad idea if it can possibly be avoided. Maybe what would work would be to have a second combinat repository. This would have to be rebased this regularly with the main sage repository. Maybe the master branches would be identical. In other words, someone would rebase the master branch on the combinat repository with the master branch on the main repository. This would not be difficult, maybe it could be automated. But the combinat repo would have many branches, and rebasing these would be the responsibility of their owners. So there would be two main repositories: sage-main <--> sage-combinat (with many branches) and the master branch would have to be frequently rebased. Patches in the current combinat mercurial queue would correspond to branches on the combinat repository, and every branch would have to be rebased regularly to keep up with changes on the sage-main master branch. But this would be the responsibility of the patch owner, not the release manager, so the work would be distributed. And because the patches would no longer be deeply nested it would be less difficult. * If we don't fork, then is there some way we can tie all of the combinat branches together? Specifically can we list all branches which don't have ticket numbers. Is there an automatic way to remove a sage-combinat branch once it has been merged into main sage? This should not be a problem. Dan -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
