{"push_id":2764450511,"size":4,"distinct_size":3,"ref":"refs/heads/th/connection-multi-connect-rh1555012","head":"0b7ff4de28819ee0a81a181ec078201e94408e04","before":"a03177274c731d659897b8b8660f33bc8a9ea217","commits":[{"sha":"4444db6b6f930f6633b1274121665cc1f8c4fc90","author":{"name":"Thomas Haller","email":"16e26612e4159990a6b3691e92592e691ff74132@redhat.com"},"message":"libnm: avoid deadlock during g_module_open() in _nm_utils_init()\n\n_nm_utils_init() is a __attribute__((constructor)) function,\nthat is, it runs during dlopen().\n\nOn the other head, g_module_open() itself calls dlopen().\n\nIt is prone to deadlock. Don't do it.\n\nThe check is only an aggressive assertion to crash the application\nif it wrongly loads libnm and libnm-util/libnm-glib at the same time.\nIf that happens, all is lost already. We can just as well call the\nassertion later. It's not supposed to fail anyway.\n\nhttps://bugzilla.gnome.org/show_bug.cgi?id=796804","distinct":false,"url":"https://api.github.com/repos/freedesktop/NetworkManager/commits/4444db6b6f930f6633b1274121665cc1f8c4fc90"},{"sha":"75f32ba5c2a99a5156f2a4a1a3b9804a5a1cec3a","author":{"name":"Thomas Haller","email":"16e26612e4159990a6b3691e92592e691ff74132@redhat.com"},"message":"all: add connection.multi-connect property for wildcard profiles\n\nAdd a new option that allows to activate a profile multiple times\n(at the same time). Previoulsy, all profiles were implicitly\nNM_SETTING_CONNECTION_MULTI_CONNECT_SINGLE, meaning, that activating\na profile that is already active will deactivate it first.\n\nThis will make more sense, as we also add more match-options how\nprofiles can be restricted to particular devices. We already have\nconnection.type, connection.interface-name, and (ethernet|wifi).mac-address\nto restrict a profile to particular devices. For example, it is however\nnot possible to specify a wildcard like \"eth*\" to match a profile to\na set of devices by interface-name. That is another missing feature,\nand once we extend the matching capabilities, it makes more sense to\nactivate a profile multiple times.\n\nSee also https://bugzilla.redhat.com/show_bug.cgi?id=997998, which\npreviously changed that a connection is restricted to a single activation\nat a time. This work relaxes that again.\n\nThis only adds the new property, it is not used nor implemented yet.\n\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1555012","distinct":true,"url":"https://api.github.com/repos/freedesktop/NetworkManager/commits/75f32ba5c2a99a5156f2a4a1a3b9804a5a1cec3a"},{"sha":"c94f7771f789b6583a9668f65e5eb8fd2ea3de0b","author":{"name":"Thomas Haller","email":"16e26612e4159990a6b3691e92592e691ff74132@redhat.com"},"message":"core: extend nm_manager_get_activatable_connections() for autoconnect and multi-connect\n\nIn general, a activatable connection is one that is currently not\nactive, or supports to be activatable multiple times according to\nmulti-connect setting. In addition, during autoconnect, a profile\nwhich is marked as multi-connect=manual-multiple will not be avalable.\nHence, add an argument \"for_auto_activation\".\n\nThe code is mostly unused but will be used next (except for connections,\nwhich set connection.multi-connect=multiple).","distinct":true,"url":"https://api.github.com/repos/freedesktop/NetworkManager/commits/c94f7771f789b6583a9668f65e5eb8fd2ea3de0b"},{"sha":"0b7ff4de28819ee0a81a181ec078201e94408e04","author":{"name":"Thomas Haller","email":"16e26612e4159990a6b3691e92592e691ff74132@redhat.com"},"message":"core: implement connection.multi-connect to activate profiles multiple times\n\nMake use of the new property, and implement it.\n\nSee previous commits for the reasons why.\n\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1555012","distinct":true,"url":"https://api.github.com/repos/freedesktop/NetworkManager/commits/0b7ff4de28819ee0a81a181ec078201e94408e04"}]}
{"actor":{"display_login":"fdo-mirror"}}