Chris White wrote:
>>never reassign a bug
>
>
> Ok, I have a section on how to re-assign the bug to the maintainer if you're
> the reporter, so you don't want that at all is what you're saying? Just let
> bug-wranglers handle it?
Yes, I'm pretty much saying that. Thinking back to the situatio
On 15:57 Sun 10 Jul , Daniel Drake wrote:
> How to give us lots of yummy info:
> - How to apply patches
> - How to use strace
> - How to identify a configure failure
> - and how to upload config.log
> - How to use gdb, for C apps
> - Using valgrind?
> etc
Tigger wrote a doc about writing
Shyam Mani wrote:
> As for the rest of the points you've brought up, did you have time to
> pen down answers as well? If so, could we have a look at them please?
> Some answers are obvious, but some others aren't and these points are
> quite valid and do need to be in the doc.
I haven't written an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/10/2005 08:27 PM, Daniel Drake wrote:
> As you know, I've been meaning to write one of these for a while. I've been
> keeping a list of topics I think should be mentioned. Stripping out the ones
> you have covered, here's what I have left:
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris White wrote:
> Doc is still here:
>
> http://www.gentoo.org/doc/en/bugzilla-howto.xml
>
> After a good ammount of user input the bugzilla doc has been updated. The
> new version uses ggdb3 instead of g for debugging and contains a new section
Hi Chris,
Chris White wrote:
> Doc is still here:
>
> http://www.gentoo.org/doc/en/bugzilla-howto.xml
I've just read over it in full. It looks good - thanks for writing it.
As you know, I've been meaning to write one of these for a while. I've been
keeping a list of topics I think should be men
Doc is still here:
http://www.gentoo.org/doc/en/bugzilla-howto.xml
After a good ammount of user input the bugzilla doc has been updated. The new
version uses ggdb3 instead of g for debugging and contains a new section on
testing ebuilds. Thanks goes to robbat2 for his commentary on what to im