You can file github tickets on the docs, sure. Since the documentation is open source, an even better thing to do (if you are so inclined) is to patch the docs:
https://github.com/ansible/ansible/tree/devel/docsite/rst I think covering this in multiple places can't hurt. On Sat, Nov 23, 2013 at 6:32 PM, Adam Baxter <[email protected]> wrote: > I just ran into the multiple line issue and found this thread via search. > > > > Probably should go here: >> >> http://www.ansibleworks.com/docs/YAMLSyntax.html<http://www.google.com/url?q=http%3A%2F%2Fwww.ansibleworks.com%2Fdocs%2FYAMLSyntax.html&sa=D&sntz=1&usg=AFQjCNFcwMF6F7nx0p8Uef7RFLp5CNEjNw> >> >> > Info about multiple lines doesn't seem to be there, however it's mentioned > in http://www.ansibleworks.com/docs/playbooks.html#tasks-list > > This thread seems to be the most complete source of documentation on the > topic :) > Is it worth raising a GitHub issue for "incomplete" documentation or is > the split-on-space method the preferred way of breaking long lines? > > Thanks, > Adam Baxter > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Michael DeHaan <[email protected]> CTO, AnsibleWorks, Inc. http://www.ansibleworks.com/ -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
