Coping with -Wunused-but-set-variable, first round

Cyril Brulebois kibi at
Fri May 20 08:37:56 PDT 2011

Cyril Brulebois <kibi at> (20/05/2011):
> We have a lot of hits, but with the upcoming patchset (30 patches…) we
> go down from 126 to 91; remaining parts include fb*, shrotpack*.h,
> render2swap.c stuff, which I was a bit reluctant to patch without
> thinking of it a bit. So the patchset should only have “easy to
> ACK/NACK” items.
> It's also available in my repository:
>   git:// unused-but-set-variable

And I forgot to ask this question: should I include some boilerplate
in each commit message? (Including the actual warning message wouldn't
bring much AFAICT, and would mean more work.)

If so, what? Just “Detected by -Wunused-but-set-variable, introduced
in gcc 4.6” or something similar?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <>

More information about the xorg-devel mailing list