Hi Christian--
The queue applies fine for me on plain 5.5.rc0. Maybe your guards are not
set correctly? This is what is usually the problem for me when the queue
seems to have suddenly gone wonky.
If that is the case, it can be fixed in one step by running:
sage -combinat qselect.
chee
Hi,
I have been using the sage-combinat branch from 2008 to 2010 (all of my
patches were in sage-combinat before getting on the sage trac) and then
stop using it. Here is my view of this. First I believe the following
principle is simple but very important :
Principle #1 : The priority (orderi
Hello !!
> Nathan, I think that this is the whole point that you are not seeing: we
> do work with sage and we do use trac. Extensively. Personally, I want my
> patches posted to trac as quickly as possible and merged into sage.
Yeah, perhaps I am wrong on that. I said a lot of things
> YES, but if you were working with the Sage TRAC server the patches would
> HAVE to be finalised. Please please, that's the whole point !
>
> Nathan, I think that this is the whole point that you are not seeing: we
do work with sage and we do use trac. Extensively. Personally, I want my
patch
Hi all,
In very short:
> You are totally independent of Sage, you don't *NEED* to
> contribute to have your version of it evolve
Not quite true: we do pay a heavy price for each and every patch that
is not merged: we have to keep rebasing them. I can tell you that it
*hurts*. We all
Hi,
> Thanks for doing this for me Travis and Nicolas! I've just synced and
> everything is fine.
I now have again a reliable connection to test the queue.
Unfortunately, it still didn't work for me to install sage combinat on
a plain 5.5.rc0. I had to disable Travis' 12587 due to tons of
confli
Helloo Andrew !
> I'm sure that I should drop this but...
At this level it may not hurt anymore :-)
> When ever anything gets big enough I think this starts to break down. For
> example, when I whined about the lack of documentation for the pickle jar
> the people who put this is place d
