[sage-combinat-devel] Re: sage-5.1.rc1

2012-07-11 Thread Hugh Thomas
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

[sage-combinat-devel] Re: sage-5.1.rc1

2012-07-11 Thread Hugh Thomas
Hi Nicolas-- I thought a bit harder about my question, and checked which guards 5.0 and 5.1 are selecting. My sage 5.0 does not select a guard called 5_1_rc1 or 5_1, which I guess is what it should be doing (using the new format for the guard names). I could fix that for myself using

[sage-combinat-devel] Re: sage-5.1.rc1

2012-07-11 Thread Nicolas M. Thiery
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

[sage-combinat-devel] Re: sage-5.1.rc1

2012-07-11 Thread Hugh Thomas
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,

Re: [sage-combinat-devel] Re: sage-5.1.rc1

2012-07-11 Thread Nicolas M. Thiery
On Wed, Jul 11, 2012 at 08:32:34AM -0700, Hugh Thomas wrote: (My help probably only made the process longer, but I did learn something.) Which is the point: I want to train others to do my job :-) I edited your explanation in the series file because I think it had typos,

[sage-combinat-devel] Merging issue

2012-07-11 Thread Andrew Mathas
Hi All, Sorry for breaking the queue last week. I am trying not to break it again but whenever I push a patch to the server merging returns the error message abort: branch 'default' has one head - please merge with an explicit rev I am not if I am missing something in my commit process and

[sage-combinat-devel] Re: sage-5.1.rc1

2012-07-11 Thread Hugh Thomas
Hi Nicolas-- I still have one question (though, in writing this email, I think I may have figured it out for myself). Before you fixed things, if I ran hg qselect in sage-5.0/deve/sage-combinat, then 5_1_rc1 did not appear in the list. After you fixed things, it did appear. What caused

Re: [sage-combinat-devel] Merging issue

2012-07-11 Thread Anne Schilling
Dear Andrew, Did you delete your sage-combinat folder on your local machine and then reinstall sage-combinat via sage -combinat install ? Nicolas put a new default tip in the mercurial repository. So if you are now in the non-default tip, this might explain your problems. Cheers, Anne On

[sage-combinat-devel] Re: reflection groups vs. Weyl groups and their root systems

2012-07-11 Thread tom d
Hey, all; Christian asked for a way to get a permutation group without running through the matrix representation. There's an object called the 'Numbers Game' which essentially constructs the Coxeter Group from a coxeter graph by tracking application of reflections to the simple roots. This

[sage-combinat-devel] Re: sage-5.1.rc1

2012-07-11 Thread Nicolas M. Thiery
On Wed, Jul 11, 2012 at 05:37:16PM -0700, Hugh Thomas wrote: I still have one question (though, in writing this email, I think I may have figured it out for myself). Before you fixed things, if I ran hg qselect in sage-5.0/deve/sage-combinat, then 5_1_rc1 did not appear in the