{"push_id":818460150,"size":7,"distinct_size":7,"ref":"refs/heads/nm-1-0","head":"cf1896987d779bab910f94f9e24b9aad8ca85125","before":"9796eace518c18fbde1fda1f8c4cced91e710f8c","commits":[{"sha":"5c20dd9ea36a4bc84d1a32b0e30c8906570d5b02","author":{"email":"16e26612e4159990a6b3691e92592e691ff74132@redhat.com","name":"Thomas Haller"},"message":"device: fix activating master/slave devices during stage2\n\nDuring stage2, if the slave detected that it would need to wait for\nthe master, it would return FALSE (which removes the g-idle-handler).\n\nHowever, it would not clear the activation-source, so later, when\nthe master becomes ready, its attempt to schedule stage2 again would\nresult in an error-log and the idle-handler would not be scheduled\nagain.\n\nFixes: 85ac903bb8010409c4010ba09c621780b385b9b5\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1268797\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1183444\n(cherry picked from commit c5210b322dd3d5d26d3a3adb6d2ca67a3fc387e0)","distinct":true,"url":"https://api.github.com/repos/lkundrak/NetworkManager/commits/5c20dd9ea36a4bc84d1a32b0e30c8906570d5b02"},{"sha":"7828003bf8bd21dd821ce448ebd18b8c55cc931d","author":{"email":"16e26612e4159990a6b3691e92592e691ff74132@redhat.com","name":"Thomas Haller"},"message":"device: handle master-ready before scheduling stage2\n\nDon't handle master-ready at the beginning of stage2, but instead while\nscheduling (and then possibly delaying the scheduling of stage2).\n\nThis seems more idiomatic:\n\n  When inside a stage and your part is done: call schedule-next-stage.\n  That is, always schedule the next stage, not the current one.\n  schedule-next-stage then might delay to really scheduling until the\n  device is ready for the next state.\n\nFixes: 85ac903bb8010409c4010ba09c621780b385b9b5\n(cherry picked from commit 7bbc090387d6a1c519c92d957f5746faffb9325c)","distinct":true,"url":"https://api.github.com/repos/lkundrak/NetworkManager/commits/7828003bf8bd21dd821ce448ebd18b8c55cc931d"},{"sha":"4e0882e9239bffd89fe84df74fb2f0663624fc17","author":{"email":"16e26612e4159990a6b3691e92592e691ff74132@redhat.com","name":"Thomas Haller"},"message":"device: assert that master-ready handler is not scheduled in schedule_stage2_device_config()\n\n(cherry picked from commit c41be469ab107ea2b4813bf28a1618572b78aa6a)","distinct":true,"url":"https://api.github.com/repos/lkundrak/NetworkManager/commits/4e0882e9239bffd89fe84df74fb2f0663624fc17"},{"sha":"2806fc985b05ebc760f236aa0c697bd07ac71fe0","author":{"email":"16e26612e4159990a6b3691e92592e691ff74132@redhat.com","name":"Thomas Haller"},"message":"systemd: make NetworkManager reloadable via SIGHUP\n\nSince f9e4af2, parts of the configuration can be reloaded\nby sending SIGHUP to NetworkManager. Add ExecReload option\nto service file to support reloading by sending a signal.\n\nNote that 'man 5 systemd.service' advices to use a blocking\ncommand instead of a sending a signal. Later we should add a\nD-Bus method to allow reloading synchronously. For now, this\nis better then nothing.\n\nhttps://mail.gnome.org/archives/networkmanager-list/2015-April/msg00042.html\n(cherry picked from commit a858b383c348c2a43e63be325156b68e3789441a)","distinct":true,"url":"https://api.github.com/repos/lkundrak/NetworkManager/commits/2806fc985b05ebc760f236aa0c697bd07ac71fe0"},{"sha":"b10e09ac17d687eb0eb10e59d508677c887d079e","author":{"email":"0517d8eb29a209176891315f89a61ea11bcc756e@redhat.com","name":"Jiří Klimeš"},"message":"libnm/vlan: default to vlan.flags=REORDER_HDR for new connections (rh #1250225)\n\nThe kernel defaults REORDER_HDR to 1 when creating a new VLAN, but\nNetworkManager's VLAN flags property defaulted to 0. Thus REORDER_HDR was not\nset for NM-created VLANs with default values.\n\nWe want to match the kernel default, so we change the default value for the\nvlan.flags property. However, we do not want to change the flags for existing\nconnections if the property is missing in connection files. Thus we have to\nupdate plugins for that. We also make sure that vlan.flags is always written\nby 'keyfile' when the value is default. That way new connections have flags\nproperty explicitly written and it will be loaded as expected.\n\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1250225\n\n(cherry picked from commit 687b6515980c08cdbb9734bd112a594166c4d6dd)","distinct":true,"url":"https://api.github.com/repos/lkundrak/NetworkManager/commits/b10e09ac17d687eb0eb10e59d508677c887d079e"},{"sha":"6289caf68f561adba14afa95bd4c745787407e49","author":{"email":"0517d8eb29a209176891315f89a61ea11bcc756e@redhat.com","name":"Jiří Klimeš"},"message":"ifcfg-rh: allow svTrueValue() to accept \"0\" and \"1\" values\n\nSome initscripts variables can use \"0\" or \"1\" instead of more common\n\"yes\", \"no\", for example REORDER_HDR.\n\nAnd we also write REORDER_HDR=0|1 in writer.c, so we did not read REODER_HDR\ncorrectly.\n\nFixes: ccea4425048cce8aef5a295c7d09daa6b66f596f\n(cherry picked from commit e8257af0d9324c2b9b59fa37c7283931c10defe1)","distinct":true,"url":"https://api.github.com/repos/lkundrak/NetworkManager/commits/6289caf68f561adba14afa95bd4c745787407e49"},{"sha":"cf1896987d779bab910f94f9e24b9aad8ca85125","author":{"email":"0517d8eb29a209176891315f89a61ea11bcc756e@redhat.com","name":"Jiří Klimeš"},"message":"ifcfg-rh: write REORDER_HDR as more common \"yes\", \"no\"\n\ninitscripts just search for negative values \"no\" or \"0\"\n(/etc/sysconfig/network-scripts/ifup)\n\nRelated: ccea4425048cce8aef5a295c7d09daa6b66f596f\n(cherry picked from commit ee3c6d57a45ed855186ce4e208af4d855c495e9e)","distinct":true,"url":"https://api.github.com/repos/lkundrak/NetworkManager/commits/cf1896987d779bab910f94f9e24b9aad8ca85125"}]}