Yikes, that sounds like a bug. FWIW, I think it's a good policy to never touch the main branch. When I want to test a patch, I make a new branch from the clean one, and apply the patch (or set of patches) there.
On Tue, 5 Jun 2007, Nick Alexander wrote: > > Hello all, > > sage -upgrade seems to be blowing away my committed hg patches that > have not been pushed to William yet. > > To the best of my memory, that did not happen in the past; has this > changed? Am I doing something wrong? This is getting annoying -- > it's very hard to submit patches against up-to-date releases with this > behaviour. > > Nick > > > > --~--~---------~--~----~------------~-------~--~----~ 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
