Hello !
Perhaps we should go through and convert all old tickets for once and
for all. (Not sure how many wouldn't convert cleanly though...)
Technically, it should be feasible to apply those patches to the
release on which they were based (a loong time ago !), and to turn
them into
+1 to getting rid of the sage dev scripts in favor of git-trac (first
the docs, then altogether). Hopefully it's becoming stable enough that
we should start shipping it as part of Sage?
On Fri, Jan 9, 2015 at 9:55 AM, Vincent Delecroix
20100.delecr...@gmail.com wrote:
1) should we keep the Sage
On 11.01.2015 09:38, Robert Bradshaw wrote:
Hopefully it's becoming stable enough that
we should start shipping it as part of Sage?
At first I thought so, too. But now I'm no longer sure: if you ship it
with Sage, then it will be difficult to use it if you want to work with
a patch from an
On Sunday, January 11, 2015 at 12:54:56 AM UTC-8, Martin von Gagern wrote:
On 11.01.2015 09:38, Robert Bradshaw wrote:
Hopefully it's becoming stable enough that
we should start shipping it as part of Sage?
At first I thought so, too. But now I'm no longer sure: if you ship it
with
1) should we keep the Sage dev scripts in Sage ?
2) Should we keep it in the doc ?
There is one very useful thing in the dev script: transform old
mercurial patches into git commit. There are still ticket on trac with
patches and I use this tool from time to time.
Vincent
--
You received
1) should we keep the Sage dev scripts in Sage ?
2) Should we keep it in the doc ?
There is one very useful thing in the dev script: transform old
mercurial patches into git commit. There are still ticket on trac with
patches and I use this tool from time to time.
Oh! I didn't
* Nathann Cohen nathann.co...@gmail.com [2014-12-26 19:37:55 +0530]:
1) should we keep the Sage dev scripts in Sage ?
I regularly use the dev scripts so I would prefer to keep them. I could
of course adapt to using git trac instead if they disappeared so this is
really only a preference.
julian
I regularly use the dev scripts so I would prefer to keep them. I could
of course adapt to using git trac instead if they disappeared so this is
really only a preference.
Okay. Do you have any objection to the removal of the documentation ?
We already advise people to not use them, and it
Helloo everybody !
There is no pub in a radius of 40km of where I live, so I spend my evenings
rewriting Sage's developer manual.
Tonight I have two questions for you:
1) should we keep the Sage dev scripts in Sage ?
2) Should we keep it in the doc ?
