{"push_id":814165094,"size":2,"distinct_size":2,"ref":"refs/heads/th/config-enable-bgo755935","head":"56a6d07841a40228c2728bbf0dcf9adb62d5286b","before":"667704d5b512e786ce882db4b6bdc025dd82bb10","commits":[{"sha":"8a4d77b62f33ccd08fcce733e8ff7a14fc6f739e","author":{"email":"16e26612e4159990a6b3691e92592e691ff74132@redhat.com","name":"Thomas Haller"},"message":"config: allow to enable/disable configuration snippets\n\nSupport a new configuration option\n\n  [.config]\n  enable=<ENABLED>\n\nfor configuration snippets.\n\nThis new [.config] section is only relevant within the snippet itself\nand it is not merged into the combined configuration.\n\nCurrently only the \"enable\" key is supported. If the \"enable\" key is\nmissing, it obviously defaults to being enabled. It allows snippets\nto be skipped from loading. The main configuration \"NetworkManager.conf\"\ncannot be skipped.\n\n<ENABLED> can be a boolean value (false), to skip a configuration\nsnippet from loading.\nIt can also be a string to match against the NetworkManager version,\nlike \"enable=nm-version-min:1.1.0,nm-version-min:1.0.6\"\n\nThere are several motivations for this:\n\n- the user can disable an entire configuration snippet by toggeling\n  one entry.\n\n- this generalizes  the functionality of the global-dns.enable\n  setting, but in a way that applies to configuration on a per-file\n  basis.\n\n- for developing, we often switch between different versions of\n  NetworkManager. Thus, we might want to use different configuration.\n  E.g. before global-dns options, I want to use \"dns=none\" and manage\n  resolv.conf myself. Now, I can use global-dns setting to do that.\n  That can be achieved with something like the following (not exactly,\n  it's an example only):\n\n      [.config]\n      enable=nm-version-min:1.1.0\n      [main]\n      dns=default\n      [global-dns-domain-*]\n      nameserver=127.0.0.1\n\n  Arguably, this would be more awesome, if we would bump our micro devel\n  version (1.1.0) more often while developing 1.2.0 (*hint*).\n\n- in principle, packages could drop configuration snippets and enable\n  them based on the NetworkManager version.","distinct":true,"url":"https://api.github.com/repos/NetworkManager/NetworkManager/commits/8a4d77b62f33ccd08fcce733e8ff7a14fc6f739e"},{"sha":"56a6d07841a40228c2728bbf0dcf9adb62d5286b","author":{"email":"16e26612e4159990a6b3691e92592e691ff74132@redhat.com","name":"Thomas Haller"},"message":"config: drop global-dns.enable option in favor of .config.enable\n\nNo longer support disabling the global-dns configuration via the\n\"enable\" option.\n\nInstead, the user can put the entire dns-configuration in one separate\nsnippet, and disable it altogether with \".config.enable\".","distinct":true,"url":"https://api.github.com/repos/NetworkManager/NetworkManager/commits/56a6d07841a40228c2728bbf0dcf9adb62d5286b"}]}