On Saturday, 21 March 2015 20:02:23 UTC+1, Felix Frank wrote: > > On 03/19/2015 12:19 PM, Bostjan Skufca wrote: > > > > I think my note about suggesting git's way of providing "plumbing and > > porcelain" interfaces as good approach still stands. > > I'm not so sure, actually. > > How exactly would you go about segregating the existing configuration > options into two categories? I don't feel that the interface lends > itself well to that. >
I am not talking about changing configuration options themselves, nor about changing how configuration file looks like (by, for example, providing new sections). I am talking about marking configuration settings as "basic" or "advanced" and then using this "discriminatory value" when writing (or generating) documentation. b. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/7acf5a9d-18b8-46a8-a023-c3e90fc40cef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
