Timeline for mutt list by vinc17
-
I hate these blogs that modify what I've written in my comment (e.g. changing " into «). This is sometimes meaningless!
-
Blog: mpfr.org Server Scheduled Downtime - http://www.vinc17.net/blog/
-
I've submitted a patch for !Mutt bug 3005: http://dev.mutt.org/trac/ticket/3005 almost all colors are bright if bright is used for "normal"
-
Blog: MPFR-MPC Developers Meeting, 25-27 June 2012 - http://www.vinc17.net/blog/
-
!MPFR in Debian Popularity Contest: libmpfr4 installed on 67% of the machines and used regularly on 53% of the machines.
-
!Debian # apt-get update; apt-get install debian-handbook
-
But I use Tab Mix Plus. I don't know if it has an influence.
-
No problem to move tabs with #Iceweasel.
-
I've received a mail from Raphaël: the !Debian Administrator's Handbook is now available under free licenses: http://debian-handbook.info/
-
!Debian grep 2.12-1 is broken: the --exclude option no longer works. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672240
-
Blog: Patches 9 and 10 for GNU MPFR 3.1.0 - http://www.vinc17.net/blog/
-
Patch 10 for GNU !MPFR 3.1.0 is available: http://www.mpfr.org/mpfr-3.1.0/#bugs - It avoids a possible freeze in the mpfr_gamma function.
-
glad to read that @raphaelhertzog and lolando's book will be released under a DFSG-free license http://ur1.ca/95gk0 !debian
-
!debian's administrator handbook : "liberation fund completed, release in the next few weeks" http://ur1.ca/94kcw
-
In !GCC attributes, always use the version with underscores to avoid potential clashes: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53182 !c
-
Blog: MPFR Mailing-Lists Scheduled Downtime - http://www.vinc17.net/blog/
-
#AlloCine a une API. Excellent! http://wiki.gromez.fr/dev/api/allocine_v3
-
A discussion on pointer sizes depending on the type in !C and !GCC: http://gcc.gnu.org/ml/gcc/2012-04/msg00864.html
-
I'm also often logged out. But this problem has occurred since yesterday for me (perhaps I don't use !identica often enough, though).
-
Yes, the numbers are different for the ipv6 group. For my home page, the error now appears in page 2.