2017-April Archive by Thread
Messages are ordered newest-to-oldest in this index. The newest
threads will be at the top of this page, the oldest will be at the bottom.
Within a single thread, the first mail note is the START of the
thread; the notes following that are in the chronological order of
when they were received. So globally, newest messages are at the top,
but within a thread, the oldest (the start of the thread) is at the
top.
If you think about it, it is confusing. Just go with the flow and everything will be all right.
Mycroft GNOME Shell Extension & Request to join the community,
Rahul Mehra
For projects switching to Meson *only*,
Emmanuele Bassi
Adding a "distraction free" mode to maximized windows?,
Alex G.S.
GNOME Build situation and BuildStream,
Tristan Van Berkom
Multimedia keys API regression in gnome-settings-daemon 3.24,
Bastien Nocera
3.26 Feature Planning,
Allan Day
pygobject: Plan to depend on a new pycairo fork,
Christoph Reiter
Multi-Seat custom.conf file configuration,
Perry, Kenny
Re: GUADEC 2017 call for talk submissions,
Sam Thursfield
Re: GNOME goal candidates,
Sébastien Wilmet
Gnu/Gnome/Linux/Ubuntu? I'm confused,
J Wilson
GNOME 3.24.1,
Matthias Clasen
Re: Fractional Scaling on Wayland,
aday
Re: About maintenance of Bijiben,
Ondrej Holy
Re: Develop of gnomeradio,
Jonathan Kang
Removing libgdict from GNOME Dictionary,
Emmanuele Bassi
Gnome3 shell is still poor, needs changes,
Erik Chendo Tegon
Fwd: Proposal: revisiting menus in Gnome,
Greg K Nicholson
GitHub Development Platform for GNOME,
Walter Vargas
Re: gtk-doc goes python,
Sébastien Wilmet
GSoC Mentors to select students proposals,
Carlos Soriano
Librsvg 2.40.17 is released (thumbnailer fix),
Federico Mena Quintero
Ubuntu 18.04 To Ship with GNOME Desktop,
Kunaal Jain
Re: GNOME 3.25/3.26 Schedule available,
Sébastien Wilmet
Help Needed | Conferences for 2017 and 2018,
Nuritzi Sanchez
Re: Clarification on license of gdbus-codegen generated code,
Jens Georg
Do not use -Werror by default in your modules without joining #testable,
Emmanuele Bassi
- Re: Do not use -Werror by default in your modules without joining #testable,
Michael Catanzaro
- Re: Do not use -Werror by default in your modules without joining #testable,
Emmanuele Bassi
- Re: Do not use -Werror by default in your modules without joining #testable,
Sébastien Wilmet
- Re: Do not use -Werror by default in your modules without joining #testable,
Emmanuele Bassi
- Re: Do not use -Werror by default in your modules without joining #testable,
Sébastien Wilmet
- Re: Do not use -Werror by default in your modules without joining #testable,
philip . chimento
- Re: Do not use -Werror by default in your modules without joining #testable,
Emmanuele Bassi
- Re: Do not use -Werror by default in your modules without joining #testable,
Sébastien Wilmet
- Re: Do not use -Werror by default in your modules without joining #testable,
Michael Catanzaro
- Re: Do not use -Werror by default in your modules without joining #testable,
Emmanuele Bassi
- Re: Do not use -Werror by default in your modules without joining #testable,
Michael Catanzaro
- Re: Do not use -Werror by default in your modules without joining #testable,
Sébastien Wilmet
- Re: Do not use -Werror by default in your modules without joining #testable,
Michael Catanzaro
- Re: Do not use -Werror by default in your modules without joining #testable,
Sébastien Wilmet
- Re: Do not use -Werror by default in your modules without joining #testable,
Nicolas Dufresne
Mail converted by MHonArc