Hi Nicolas-- I agree that the (now only two) patches that don't apply to 5.1.rc1 are now applied to 5.0 and guarded from 5.1. Success! (My "help" probably only made the process longer, but I did learn something.)
I edited your explanation in the series file because I think it had typos, including some which were potentially confusing. Please check that what is now there makes sense (when you have a minute). Could you please explain what you did so that now my sage-5.0 sage -combinat update knows to select the 5_1_rc1 guard when before, it didn't? cheers, Hugh On Wednesday, July 11, 2012 5:44:57 PM UTC+3, Nicolas M. Thiery wrote: > > On Wed, Jul 11, 2012 at 01:30:11AM -0700, Hugh Thomas wrote: > > Hi Nicolas, hi Christian, Mike, and Andrew (whose patches I > guarded)-- > > > > Nicolas, I added the guard +sage_5_1_rc1 on the three patches which > don't > > apply to sage-5.1.rc1, but this guard does not get selected by > someone > > running sage-5.0. (Andrew pointed this out, and I have the same > > experience with my copy of 5.0.) > > The guard should be ``+5_1_rc1''. Guards of the form ``sage_...'' were > used with the sage-combinat script for Sage <= 4.8. I just fixed the > series, and used the occasion to remove old cruft to avoid future > confusion. > > Please double check, and thanks for investigating! > > Cheers, > Nicolas > -- 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/-/oXUCkd9KrLwJ. 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.
