(Say that subject three times fast.)
I'm looking at a ticket whose main purpose is to apply the
@rename_keyword decorator in lots of places, outside of the plot
module, where it was first employed.
When I build the HTML version of the reference manual, it would appear
these functions are now list
+1 to Rob Beezer's comments. I don't have anything to add to them,
other than my agreement - very well said.
-Marshall Hampton
On Sep 15, 8:50 pm, Rob Beezer wrote:
> We are all adults here. Well mostly, excluding some child-prodigy-
> developers we have.
>
> Policy is for people who have no j
We are all adults here. Well mostly, excluding some child-prodigy-
developers we have.
Policy is for people who have no judgment. I just read a ticket where
Robert Miller said, "Take it to sage-devel." Burcin took another
ticket I was in on to sage-devel. A third ticket got sent back to
"needs
On Mon, Sep 13, 2010 at 3:37 AM, David Kirkby wrote:
>>> True. But if person A creates the ticket, person B reviews it and the
>>> release manager finds it passes, it may end up getting merged.
>>
>> I see that as someone not doing there job properly if we were to decide that
>> a vote is required
Dear David,
Your post finds me in a very good mood. I just went out for a walk to
think about my graphs and found out again that I loved the sight of a
deep blue sky, small streets, seagulls and sea more than any other.
There can be no better background for a graph problem :-)
> You were cc'ed on
This might be of interest on security grounds:
http://www.amazon.com/Secure-Coding-Robert-C-Seacord/dp/0321335724
On 9/15/2010 6:46 AM, Dr. David Kirkby wrote:
On 09/15/10 06:17 AM, Minh Nguyen wrote:
I'm disheartened that this happened. One should not modify upstream
source, but place patche
On 09/14/10 01:48 PM, Nathann Cohen wrote:
David,
I tried 10 times to give an answer to your message, but none managed
to stay very calm after the 5th line. I still have great hopes for the
following attempt.
First, I remember having said once on this mailing list -- but perhaps
it was not to y
On 09/15/10 06:17 AM, Minh Nguyen wrote:
I'm disheartened that this happened. One should not modify upstream
source, but place patches against upstream source under the directory
patch/.
I think you mean "patches". I did notice a "patch" directory in Cliquer, but
http://www.sagemath.org/doc/d
On 09/15/10 11:01 AM, Nathann Cohen wrote:
If, as Dima mentionned it, I was meant to read this whole conversation
as a "Nathann, could you update the Cliquer SPKG so that your
modifications only appear in a patch folder" (and at some point the
whole of Cliquer's source was in this patch/ folder),
> If, as Dima mentionned it, I was meant to read this whole conversation
> as a "Nathann, could you update the Cliquer SPKG so that your
> modifications only appear in a patch folder" (and at some point the
> whole of Cliquer's source was in this patch/ folder), this would
> indeed require very few
> Hi Nathann,
Hello Minh !
> I'll be looking into the Cliquer spkg. I hope you would answer any
> questions I have regarding that spkg or about computing cliques.
I would and I will.
If, as Dima mentionned it, I was meant to read this whole conversation
as a "Nathann, could you update the Clique
Hi Jan,
On Wed, Sep 15, 2010 at 3:43 PM, Jan Groenewald wrote:
> Is there a sage-devel code of conduct (like Ubuntu's perhaps -- it could
> easily be adapted from that)?. It might be a good addition.
I have been collecting some information [1] on managing an open source
community, with a view to
Hi David,
On Wed, Sep 15, 2010 at 12:01 AM, Dr. David Kirkby
wrote:
> I had my suspicions it was you, but I was not sure - I had no intentions of
> accusing anyone unless I was sure. I had in fact cc'ed you on the ticket,
> but you made no comments whatsoever.
I also touched the Cliquer spkg, so
Hi Nathann,
On Tue, Sep 14, 2010 at 10:48 PM, Nathann Cohen wrote:
> If by any miracle you still ignored that I wrote this (very poor --
> let me add it for you) interface and all the functions of Sage that
> use Cliquer, you will find my name under the "SPKG Maintainer" field
> of the SPKG.txt f
14 matches
Mail list logo
