Hi, > Could you "rebase" the entire Sage repo so it has the new hashes, then > included > it for Sage-3.0 :-) If we're going to make a massive change like > that, 3.0 would > be the time to do it. Or does that request make no sense?
We will likely have the same problem every time we merge heads if I understand the problem correctly. We also have about 40 patches outstanding [at any given time it seems - the number seems to oscillate around 40] and all of those would need to be rebased. Since the repo-as-text is a very specific case and in case it would have to be redone after each branch merge I see little benefit to do it. > Wiliam Cheers, Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
