Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Cleaning up bugs

Hi Tim,

Glad to hear you're interested in learning the codebase and fixing some bugs :)

For the bugs you mentioned, I would say go ahead and close them, assuming you have the relevant Bugzilla permissions. (I would have closed them myself, but I don't have the Bugzilla permissions to do so, and last I asked, I was told only committers get those permissions.)

If you'd like some suggestions for Codan bugs you could fix while learning the codebase, I have some in mind; if you'd like, I can also give you pointers/guidance about how to approach them.


> From: tim@xxxxxxxxxxxxxxxx
> To: cdt-dev@xxxxxxxxxxx
> Date: Mon, 10 Aug 2015 20:11:13 +0100
> Subject: [cdt-dev] Cleaning up bugs
> Hi all,
> I was looking through the Codan bugs to see if there was anything I
> could tackle while I try and learn the codebase. I very quickly stumbled
> across some bugs (e.g. #356908, #348386) that seem to already have been
> fixed. There are no new reports in a year or more, and I've tried the
> reproduction cases out in my own build and satisfied myself that they
> work. Is it acceptable for me to mark things like this as closed as I
> encounter them, or is there a more formal process I should follow?
> Thanks,
> Tim
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top