I could certainly look into writing the modification - I've written a shell script or ten in my day. How much different is the process for patching up the combinat script as opposed to the main sage sources?
Cheers, -tom On Tuesday, October 16, 2012 11:50:10 AM UTC+3, Nicolas M. Thiery wrote: > > On Tue, Oct 16, 2012 at 01:31:11AM -0700, tom d wrote: > > Is there a way to (easily) check whether there are updates on the > mercurial > > server without popping all patches, reapplying, and rebuilding?� With > the > > amount of cython in the queue, it's taking quite a while for sage to > rebuild > > itself after each check.� I just want to check that there are no > changes, then > > commit (or update if there are changes)!� In fact, if possible, this > should > > probably be the default behaviour for 'sage --combinat update'. > > cd <sage>/devel/sage-combinat/.ht/patches > hg incoming > > I agree that this would be a nice and easy to implement feature of the > sage-combinat script. Volunteers? > > Cheers, > Nicolas > > PS: It could even be fancy and only pop off those patches that > have been modified (but that's tricky, because we need to check the > series as well). > > -- > Nicolas M. Thi�ry "Isil" <nth...@users.sf.net <javascript:>> > http://Nicolas.Thiery.name/ > -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/CMv6ZW4jS5YJ. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
