Hi Everyone,
I really enjoyed ICERM last week and I found it quite productive.
I have just uploaded my review patch of #13605. I am posting news of this
here because in order to get the queue to apply I needed to make trivial
rebases of
- trac_8703-trees-fh.patch
- trac_14086-parking_fu
Hi Travis and Nicolas,
Thanks for your replies. I was hoping for something less drastic as
whatever I have done affects all of the installations of sage that I have.
Still, this seems to work:)
By reinstalling I have fixed the problem, feel please free to ignore this
but I am still curious as
Hey Andrew,
There's always the draconian way of doing things: copy the patch to a
separate local (this is the uber important step), delete the combinat
branch, and reinstall combinat. Other than that, I have no clue as to what
happened, much less how to fix it in place.
Best,
Travis
On Sun
On Sun, Feb 17, 2013 at 02:58:27PM -0800, Andrew Mathas wrote:
>Hello!
>
>I'm trying to push patches for #13605-review and #1410[34] but I seem to
>have screwed up where hg thinks home is.
>
>I think that what I must have done is somehow got hg to sync with a local
>repositor
Hello!
I'm trying to push patches for #13605-review and #1410[34] but I seem to
have screwed up where hg thinks home is.
I think that what I must have done is somehow got hg to sync with a local
repository rather than with the queue. The reason that I think this might
be the problem is that `
Hey everyone,
Mike Z. first noticed that the docbuild crashes when the full combinat
queue is applied, and the patch which this starts to occur is Mike H.'s
attrcall-mh.patch.
travis@travis-virtualbox:~/sage-5.7.beta3/devel/sage-combinat/sage/combinat$
sage -docbuild reference html
sphinx-bu
2013/2/17 Anne Schilling :
> On 2/17/13 9:36 AM, Volker Braun wrote:
>> Just to relay a comment that I made on #14144. The IPython update broke
>> branch printing and nobody noticed for a while. So I removed it. There are a
>> number of ways to find out the branch very easily:
>>
>> * Just "hg br
On Sun, Feb 17, 2013 at 09:36:44AM -0800, Volker Braun wrote:
>Just to relay a comment that I made on #14144. The IPython update broke
>branch printing and nobody noticed for a while. So I removed it. There are
>a number of ways to find out the branch very easily:
>* Just "hg branch
On 2/17/13 9:36 AM, Volker Braun wrote:
> Just to relay a comment that I made on #14144. The IPython update broke
> branch printing and nobody noticed for a while. So I removed it. There are a
> number of ways to find out the branch very easily:
>
> * Just "hg branch", without even starting Sage
Ooops. My mistake... a qselect problem
2013/2/17 Vincent Delecroix <20100.delecr...@gmail.com>:
> Hi,
>
> I use sage-5.7.beta4 and combinat does not apply
> {{{
> application de trac_14065-combinatorial_object_cmp-ts.patch
> patching file sage/categories/crystals.py
> Hunk #1 FAILED at 518
> 1 out
Hi,
I use sage-5.7.beta4 and combinat does not apply
{{{
application de trac_14065-combinatorial_object_cmp-ts.patch
patching file sage/categories/crystals.py
Hunk #1 FAILED at 518
1 out of 3 hunks FAILED -- saving rejects to file
sage/categories/crystals.py.rej
}}}
Best
Vincent
--
You received
Just to relay a comment that I made on #14144. The IPython update broke
branch printing and nobody noticed for a while. So I removed it. There are
a number of ways to find out the branch very easily:
* Just "hg branch", without even starting Sage
* Look at the devel/sage symlink
* From within Sa
On Sunday, February 17, 2013 6:15:05 AM UTC-8, Mike Zabrocki wrote:
>
> BTW, I found the answer to my first question:
> sage: from sage.misc.misc import branch_current_hg
> sage: branch_current_hg()
>
> This is returning the correct branch name.
>
The command
sage: version(clone=True)
incl
BTW, I found the answer to my first question:
sage: from sage.misc.misc import branch_current_hg
sage: branch_current_hg()
This is returning the correct branch name.
-Mike
On Sunday, 17 February 2013 09:03:00 UTC-5, Mike Zabrocki wrote:
>
>
> It usually tells you when starting sage (nothing for
On 2/17/13 6:03 AM, Mike Zabrocki wrote:
>
> It usually tells you when starting sage (nothing for main, or "current
> brench is: ..." otherwise). You can also go to the order devel and
>
> I think something is wrong here.
> I checked that symbolic link is pointing to a cloned branch.
> Wh
> It usually tells you when starting sage (nothing for main, or "current
> brench is: ..." otherwise). You can also go to the order devel and
I think something is wrong here.
I checked that symbolic link is pointing to a cloned branch.
When I start up, it is running the cloned branch and it doe
> When I start up sage-5.7.beta3 it doesn't tell me what branch I am using.
> Is there a way to tell?
> If there is a command in sage like 'branch()' it would be helpful. How do I
> find it?
It usually tells you when starting sage (nothing for main, or "current
brench is: ..." otherwise). You can
Hi,
When I start up sage-5.7.beta3 it doesn't tell me what branch I am using.
Is there a way to tell?
If there is a command in sage like 'branch()' it would be helpful. How do
I find it?
-Mike
--
You received this message because you are subscribed to the Google Groups
"sage-combinat-devel
18 matches
Mail list logo
