bugzilla & word wrapped text

bugzilla & word wrapped text

[Jamie Lenehan]

Is there anyway to stop bugzilla from word wrapping the text that's
placed in bug reports? It makes any sort of command output and
code/patches etc pretty damn difficult to make sense of.

-- 
 Jamie Lenehan <lenehan@twibble.org>

Re: bugzilla & word wrapped text

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jamie Lenehan schreef:
> Is there anyway to stop bugzilla from word wrapping the text that's
> placed in bug reports? It makes any sort of command output and
> code/patches etc pretty damn difficult to make sense of.

You can, by using the 'attach' feature, which is sadly only visible after creating the
inition bugreport. It's like inline patches in email, the kernel dudes love'em, I hate
them :). The ideal bugreport would be:

* someone files bug and puts a summarized error message in the comment
* that person opens the bug again and attaches full log
* some guru has a fix and attaches the path
* patch will be applied and bug closed.

Sounds good?

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFFMJ4rMkyGM64RGpERAjAvAJ4jXHx9SD+2D+yoL0KokF/wT13PLQCdFIte
Sy7Oq0HCL2fHO8EjMsGLXEs=
=IxHy
-----END PGP SIGNATURE-----

Re: bugzilla & word wrapped text

[Jamie Lenehan]

On Sat, Oct 14, 2006 at 10:22:03AM +0200, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Jamie Lenehan schreef:
> > Is there anyway to stop bugzilla from word wrapping the text that's
> > placed in bug reports? It makes any sort of command output and
> > code/patches etc pretty damn difficult to make sense of.
> 
> You can, by using the 'attach' feature, which is sadly only visible after creating the
> inition bugreport. It's like inline patches in email, the kernel dudes love'em, I hate
> them :). The ideal bugreport would be:

The entire attachement setup on bugzilla sucks, but I agree for
patches and logs it should be used. I wish it had some damn option to
view them inline instead of usually having to download the damn
attaches and then go and find and view them in some other program
though (and even better if it did it by default so I don't have to go
the attachments page to view it!)

But I was more talking about trying to discuss stuff, like this from
a recent bug of mine:

---
The headers for glibc now define PT_GETSIGINFO:

 %> find tmp/staging -name '*.h' -exec grep -H PT_GETSIGINFO {} \;
 tmp/staging/sh4-linux/include/sys/ptrace.h:#define PT_GETSIGINFO
PTRACE_GETSIGINFO

where as they didn't for glibc 2.4. This causes the code in strace.c to fail
since in enables code that uses PT_CR_IPSR and PT_CR_IIP which are only
definied for IA64.
---

This is a trivial example, since only 1 lione was wrapped, but it
should have looked like this which is far easy to read:

---
The headers for glibc now define PT_GETSIGINFO:

 %> find tmp/staging -name '*.h' -exec grep -H PT_GETSIGINFO {} \;
 tmp/staging/sh4-linux/include/sys/ptrace.h:#define PT_GETSIGINFO PTRACE_GETSIGINFO

where as they didn't for glibc 2.4. This causes the code in strace.c to fail
since in enables code that uses PT_CR_IPSR and PT_CR_IIP which are only
definied for IA64.
--

Especially when you have a lot to say in the bug.

-- 
 Jamie Lenehan <lenehan@twibble.org>