chicken-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] Re: [Chicken-bugs] #227: csc segfaults with certain


From: Brandon Van Every
Subject: Re: [Chicken-users] Re: [Chicken-bugs] #227: csc segfaults with certain recursive sources
Date: Sat, 26 May 2007 13:26:02 -0400



On 5/26/07, Dan Muresan <address@hidden> wrote:
> I've noticed the messed up single-newline behavior as well.  You could
> file an "infrastructure" bug.  :-)  Assign it to Arto, he deals with
> Trac stuff.  Also let us know in ticket #164 whether you were able to
> assign it or not.  If so, then #164 should be closed.  If not, then #164
> "can't assign stuff" is still a bug.  :-)

Man, if you've noticed it first then maybe *you* should submit a new
ticket, instead of asking me to do it. I think it's only fair.

Thanks for registering in Trac and submitting what you've already submitted.  Working with the Trac process helps all of us immensely and improves Chicken.

But, let's not get into "you should do the work... no, you should!"  An open source community grows by people pitching in, especially for very minor things that are easy enough for them to do.  Putting things in bug trackers is work; it is my policy to condition as many people as possible in the Chicken community to do the work.  Anything that can be delegated, especially really minor things like a bug of this stature, should be delegated so that the load on core Chicken developers is reduced.  I've got 3 active tickets in Trac I should be working on; you do not.  I don't expect anyone to volunteer to actually fix things, but my point is, I am carrying my weight and am sufficiently busy.

That is not to mention projects / life priorities aside from Chicken, either.  I'm sure you have yours as well.  If you don't want to do something right this minute, I might suggest marking an e-mail as Unread and dealing with it later.  But I do hope in general, people will take the time to submit issues to the bug tracker.  Otherwise people forget.  That's pretty much what a bug tracker is for, to aid memory.


I don't know what #164 is (and I don't see a way to quickly jump to a
ticket by number),


Hm you're right, this isn't obvious.  Typing "#164" into the Search field works, but how would anyone know to do that?  I've added http://trac.callcc.org/ticket/229 about that.


nor do I really care that much right now, to be honest...


If so, why would you criticize me for not having filed the single-newline bug earlier?
 

Cheers,
Brandon Van Every



reply via email to

[Prev in Thread] Current Thread [Next in Thread]