An easy way to impliment this would be using the keywords field. afaik there is no way to tell if an attachment is a patch, image, binary, etc.
I propose we use some standard keywords, e.g. tg|has_patch tg|patch_tested tg|to_commit etc. That way custom reports can be set up with ease searching simply on the keywords. These keywords are just examples, and could/should be changed to fit our needs. Does this sound like a good idea? Lee On 21/11/05, Michele Cella <[EMAIL PROTECTED]> wrote: > > Regarding Kid, I've also made a trivial patch for TG ticket 59. > > http://trac.turbogears.org/turbogears/ticket/59 > > Ciao > Michele > > PS > I think we should setup a custom trac report to show pending patches. > > David Stanek wrote: > > I have posted a patch to the kid trac > > http://lesscode.org/projects/kid/ticket/66. This fixes the issue where > > having a comment in a template that extends another causes a failure. > > > > Related tickets: > > Kid: http://lesscode.org/projects/kid/ticket/66 > > TurboGears: http://trac.turbogears.org/turbogears/ticket/71 > > > > If you try the patch let me know how it works for you. Tomorrow morning I'll > > see if I can post a blog entry describing the problem. > > > > -- David > >
