2015-March 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.

  • [PATCH 1/1] core: add "fatal-warnings" option to NM_DEBUG, Thomas Haller
  • Fwd: HELP ME!!!, Iván Sánchez Vallejo
  • Some problems of NetworkManager, 张天晔
  • seeing "activation stage already scheduled" failure with NetworkManager-, Adam Goode
  • Build Error on Raspberry Pi, Jordan Messina
  • AP support, Michal Strnad
  • Connection failed to be established: privat-key-password-failure, Thomas Schneider
  • NM-Manager 0.9.10 | Debian Jessie | Connection Editor fuckup, system_error
  • Should network-manger manage virbr0 ?, Franck Routier (perso)
  • [PATCH 1/1] examples: bash: print errors int stderr, Petr Vorel
  • NMClient.IP4Config get_addresses() not always populated when signal 'notify::ip4-config' is fired, Sylvain Garaud
  • Power management in NM, Andrey Batyiev
  • Maintaining connection, Alex Ferm
  • [PATCH 1/1] examples: python: print into stderr, Petr Vorel
  • NetworkManagerFailed to read classid file: Object not found, Ali Nematollahi
  • No (more) OpenVPN on Debian8 (Jessie), system_error
  • [review] backport th/uuid-duplicate-rh1171751 to nm-1-0, Thomas Haller
  • ANN: NetworkManager released, Dan Williams
  • [review] dcbw/nm-0-9-10-slaves, Dan Williams
  • D-bus create device, tutorials, resources, Petr Horacek
  • No more IPv4 address after boot up since NM 0.9.10, Frederik Himpe

  • Mail converted by MHonArc