7 Commits (57e51f7fdf2b3a2894abcf8221709bb77ae29d36)

Author	SHA1	Message	Date
Daniel Hokka Zakrisson	073fb21bcb	Document that task includes are now infinite depth	12 years ago
Dag Wieers	66fb7fd9de	Make use of yes/no booleans in playbooks ... At the moment Ansible prefers yes/no for module booleans, however booleans in playbooks are still using True/False, rather than yes/no. This changes modifies boolean uses in playbooks (and man pages) to favor yes/no rather than True/False. This change includes: - Adaptation of documentation and examples to favor yes/no - Modification to manpage output to favor yes/no (the docsite output already favors yes/no)	12 years ago
Serge van Ginderachter	d04bd04f80	typo in handlers example yaml	12 years ago
Nigel Metheringham	a457d24b97	Added comment about long lines in playbooks ... I had trouble finding this information, so though it was worth adding to docs... but am not sure its easy to find for someone specifically to find. At least I think this inclusion matches the tone of document, but maybe this info should go into a FAQ instead/as-well?	12 years ago
Michael DeHaan	0677891fc6	More docs	12 years ago
Philipp Grau	9b15b5d592	Use && for executing next command if, and only if, command1 returns an exit status of zero.	12 years ago
Michael DeHaan	d6e4b1bf5b	Subtree merge of ansible-docs	12 years ago