Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix $last_result documentation and spelling tweaks - issue #1420 #1429

Merged
merged 2 commits into from Oct 24, 2012
Merged

Fix $last_result documentation and spelling tweaks - issue #1420 #1429

merged 2 commits into from Oct 24, 2012

Conversation

nigelm
Copy link
Contributor

@nigelm nigelm commented Oct 23, 2012

No description provided.

mpdehaan added a commit that referenced this pull request Oct 24, 2012
Fix $last_result documentation and spelling tweaks - issue #1420
@mpdehaan mpdehaan merged commit 31c8bf6 into ansible:devel Oct 24, 2012
@mpdehaan
Copy link
Contributor

I was just having this conversation with a tech writer the other day who was saying tech folks spell separate wrong more than normal people.

Something to that :)

Thanks! Will be in the next doc rebuild/push.

@nigelm
Copy link
Contributor Author

nigelm commented Oct 24, 2012

Michael DeHaan wrote:

I was just having this conversation with a tech writer the other day who
was saying tech folks spell separate wrong more than normal people.

I'm always convinced it should have an "e" rather than an "a", but my
text editor helpfully puts red marking around it :-)

Going back to the last_result issue - I wonder if ansible could catch an
unknown variable in an only_if expression in a cleaner fashion than
having python throw up everywhere? I guess some of this will be dealt
with by moving to when and keeping people out of raw python...

Nigel.

[ Nigel Metheringham ------------------------------ nigel@dotdot.it ]
[ Ellipsis Intangible Technologies ]

mpdehaan added a commit that referenced this pull request Nov 20, 2012
Fix $last_result documentation and spelling tweaks - issue #1420
@ansible ansible locked and limited conversation to collaborators Apr 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants