Re: [sage-devel] Trac keywords

2010-10-25 Thread Burcin Erocal
On Sat, 23 Oct 2010 18:58:05 +0200
Jeroen Demeyer  wrote:

> I have a page on the wiki with a proposal for standard Trac keywords.
> Feel free to edit: http://wiki.sagemath.org/TracKeywords
> 
> I'm not sure that all these keywords are useful, but some of them
> certainly are.

I really like your suggestion. IMHO, if trac provided a way for
people to watch keywords instead of components, these could easily
replace the current list of components.

This suggests that roundup has such a feature:

http://trac.edgewall.org/ticket/2954

Perhaps we can achieve something similar with these plugins to trac:

http://trac-hacks.org/wiki/AnnouncerPlugin

http://trac-hacks.org/wiki/WatchlistPlugin

This also looks useful:

http://trac-hacks.org/wiki/KeywordSuggestPlugin


Cheers,
Burcin

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org


Re: [sage-devel] Trac keywords

2010-10-23 Thread Jeroen Demeyer
On 2010-10-23 19:48, Dr. David Kirkby wrote:
> I think to imply code failing with -O3 but but ok with -O1 is a gcc bug
> is wrong.
Well, I didn't really *imply* that, just said it was a *sign*.  It is
either badly written code or a gcc bug.

> From what I understand, -O3 should not break code unless it is
> badly written. Higher levels is another matter.
No -O level should ever break standard-conforming code (of course, a lot
of code is *not* standard-conforming).
There are no "higher levels, -O3 is the maximum (at least on all the gcc
versions I have used).

> But I like the idea of being notified about bugs in components I've
> agreed to take care of. This facility will disapear.
I'm not proposing this to replace the components, it could be in
addition to.

Jeroen.

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org


Re: [sage-devel] Trac keywords

2010-10-23 Thread Dr. David Kirkby

On 10/23/10 05:58 PM, Jeroen Demeyer wrote:

I have a page on the wiki with a proposal for standard Trac keywords.
Feel free to edit: http://wiki.sagemath.org/TracKeywords

I'm not sure that all these keywords are useful, but some of them
certainly are.

Jeroen.



I think to imply code failing with -O3 but but ok with -O1 is a gcc bug is 
wrong. From what I understand, -O3 should not break code unless it is badly 
written. Higher levels is another matter.


You needed a better distinction between operating system and cpu.

But I like the idea of being notified about bugs in components I've agreed to 
take care of. This facility will disapear. I'm not convinced this is a forward 
step myself.


dave

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org


[sage-devel] Trac keywords

2010-10-23 Thread Jeroen Demeyer
I have a page on the wiki with a proposal for standard Trac keywords.
Feel free to edit: http://wiki.sagemath.org/TracKeywords

I'm not sure that all these keywords are useful, but some of them
certainly are.

Jeroen.

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org