Re: 01/01: gnu: xf86-video-openchrome: Patch to correct build failure.

Re: 01/01: gnu: xf86-video-openchrome: Patch to correct build failure.

[Ludovic Courtès]

Andreas Enge <andreas@enge.fr> skribis:

> commit bc0b89bb3eca3adf35230d1fe7f89664762be4e8
> Author: Andreas Enge <andreas@enge.fr>
> Date:   Sun Nov 23 15:41:30 2014 +0100
>
>     gnu: xf86-video-openchrome: Patch to correct build failure.
>     
>     * gnu/packages/xorg.scm (xf86-video-openchrome): Add patch for build failure
>         with glibc-2.20. Fixes bug #18740.

Thanks for working on it!  In the future please use the same format as
commit 1d18d87f to refer to the bug that is fixed; having a uniform way
for that makes it easier to search for bug fixes, notably when preparing
NEWS.

Cheers,
Ludo’.

Re: 01/01: gnu: xf86-video-openchrome: Patch to correct build failure.

[Andreas Enge]

On Sun, Nov 23, 2014 at 06:13:59PM +0100, Ludovic Courtès wrote:
> Thanks for working on it!  In the future please use the same format as
> commit 1d18d87f to refer to the bug that is fixed; having a uniform way
> for that makes it easier to search for bug fixes, notably when preparing
> NEWS.

Okay! I must admit I saw it, but what I do not like about it is that when
you are on a bug with your web browser, you cannot just copy and paste
its address. For instance, the
   http://bugs.gnu.org/19119
of the bug report is redirected to
   http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19119

I find it weird to need to type a URL by hand and potentially introduce
errors.

Andreas