vyatta-cfg.git/src, branch debian/0.16 Vyatta configuration system (mirror of https://github.com/vyos/vyatta-cfg.git) https://git.amelek.net/vyos/vyatta-cfg.git/atom?h=debian%2F0.16 2009-12-02T00:50:33+00:00 remove .changes file after work was done by commit 2009-12-02T00:50:33+00:00 Michael Larson slioch@slioch.vyatta.com 2009-12-02T00:50:33+00:00 urn:sha1:c592d618c029609b7080100de639f4ccab1f680a preserve node.val order for term multinodes. fix for bug 5103 2009-11-10T20:04:23+00:00 Michael Larson mike@ft1.vyatta.com 2009-11-10T20:04:23+00:00 urn:sha1:3238b588efc4bc2766edeaec9b1d0369815186f7 Merge branch 'kenwood' of http://git.vyatta.com/vyatta-cfg into kenwood 2009-11-06T00:40:23+00:00 Bob Gilligan gilligan@vyatta.com 2009-11-06T00:40:23+00:00 urn:sha1:e098fbffec2ed1efa9a248ae449b5cf67d0a2a36 Allow inline comments in config template fields. 2009-11-06T00:39:30+00:00 Bob Gilligan gilligan@vyatta.com 2009-11-06T00:39:30+00:00 urn:sha1:5edd540c79f349cbe5f377f5b0e8ed16dcf7cf99 Also change priority.pl script to display inline comments found in "priority:" fields if they are present. fix for missing priority value on embedded multinode. bug behavior was more limited than this--at least tag node.def and multiple 2009-11-03T01:22:05+00:00 slioch slioch@eng-140.vyatta.com 2009-11-03T01:22:05+00:00 urn:sha1:89a8f27b3d905501c9097544f27dd76208303b80 configuration on commit. tested fix with limited regression test. also slightly modified break on priority values where embedded multinodes with priority values are treated as discrete transactions (which isolates failures within the multinode and not the parent of the multinode). dismantle old priority file parsing and node matching code. removed 2009-10-23T17:07:54+00:00 slioch slioch@eng-140.vyatta.com 2009-10-23T17:07:54+00:00 urn:sha1:a4a15d2cb93e9fcf56f98472694e064d82c31f94 references to old values. activate priority values from node.def. priority file is now no longer used and should be considered depricated. 2009-10-22T22:36:22+00:00 slioch slioch@eng-140.vyatta.com 2009-10-22T22:36:22+00:00 urn:sha1:ee4800de96b1fb561a1e3f612814784891b4c468 priorities should match up on all nodes now, except where the priority file diverges from the node.defs 2009-10-22T00:27:55+00:00 slioch slioch@eng-140.vyatta.com 2009-10-22T00:27:55+00:00 urn:sha1:a5e5ddbbc35fca7a33e2c14d7e4b2e068e01da51 commit behavior has not changed yet, but can be completely switched over to node.def priority system with simple change. preserve priorities in hierarchy. old priority still active, but commit -s will now display both priorities: 2009-10-21T23:52:42+00:00 slioch slioch@eng-140.vyatta.com 2009-10-21T23:52:42+00:00 urn:sha1:9817f6e3a0581263cdec34a8c914bf41052c73ed interfaces (t: 0, p: 850,850) the first value is from the old priority file and is the active value, the second value is the value retrieved from the node.def and is not used (yet). pull priority from file into data structure 2009-10-21T23:33:13+00:00 slioch slioch@eng-140.vyatta.com 2009-10-21T23:33:13+00:00 urn:sha1:7c64f480f3aaa2f6d46bf3d83c62e084e9a3154e