cron: minor fixes #50

Closed
wants to merge 3 commits into
from

Conversation

Projects
None yet
2 participants
@goblin

goblin commented Mar 21, 2013

Two minor fixes to the "cron" resource documentation.

Another thing, as maplebed pointed on IRC, would be to add some example for the command attribute, but I'm not sure what example would be good.

@jamescott

This comment has been minimized.

Show comment Hide comment
@jamescott

jamescott Mar 21, 2013

Contributor

I will make the changes locally for the asterisks needing quoting as strings and the default '*' issue. The "Merge pull request #1" I am not sure what that is trying to do and there are far to many changes in that commit to take in a single pull request.

Contributor

jamescott commented Mar 21, 2013

I will make the changes locally for the asterisks needing quoting as strings and the default '*' issue. The "Merge pull request #1" I am not sure what that is trying to do and there are far to many changes in that commit to take in a single pull request.

@jamescott jamescott closed this Mar 21, 2013

@goblin

This comment has been minimized.

Show comment Hide comment
@goblin

goblin Mar 21, 2013

Thanks, that "merge" commit was me trying to sync up digital-science's clone to upstream... everything on it should already be in opscode master.

This pullreq was basically about these 2 commits that you said you'll include - which is OK :-) thanks

goblin commented Mar 21, 2013

Thanks, that "merge" commit was me trying to sync up digital-science's clone to upstream... everything on it should already be in opscode master.

This pullreq was basically about these 2 commits that you said you'll include - which is OK :-) thanks

@jamescott

This comment has been minimized.

Show comment Hide comment
@jamescott

jamescott Mar 21, 2013

Contributor

Cool!

Thanks for the pull requests. I am asking around to see if anyone can help me find a better example for the cron resource's command attribute.

James


From: goblin [notifications@github.com]
Sent: Thursday, March 21, 2013 1:20 PM
To: opscode/chef-docs
Cc: James Scott
Subject: Re: [chef-docs] cron: minor fixes (#50)

Thanks, that "merge" commit was me trying to sync up digital-science's clone to upstream... everything on it should already be in opscode master.

This pullreq was basically about these 2 commits that you said you'll include - which is OK :-) thanks


Reply to this email directly or view it on GitHubhttps://github.com/opscode/chef-docs/pull/50#issuecomment-15262882.

Contributor

jamescott commented Mar 21, 2013

Cool!

Thanks for the pull requests. I am asking around to see if anyone can help me find a better example for the cron resource's command attribute.

James


From: goblin [notifications@github.com]
Sent: Thursday, March 21, 2013 1:20 PM
To: opscode/chef-docs
Cc: James Scott
Subject: Re: [chef-docs] cron: minor fixes (#50)

Thanks, that "merge" commit was me trying to sync up digital-science's clone to upstream... everything on it should already be in opscode master.

This pullreq was basically about these 2 commits that you said you'll include - which is OK :-) thanks


Reply to this email directly or view it on GitHubhttps://github.com/opscode/chef-docs/pull/50#issuecomment-15262882.

@jamescott

This comment has been minimized.

Show comment Hide comment
@jamescott

jamescott Mar 21, 2013

Contributor

OK. Some examples (quickly published), but hopefully they help provide more insight into what the command attribute can do within the context of the cron resource.

http://docs.opscode.com/resource_cron.html

James


From: James Scott
Sent: Thursday, March 21, 2013 1:55 PM
To: opscode/chef-docs
Subject: RE: [chef-docs] cron: minor fixes (#50)

Cool!

Thanks for the pull requests. I am asking around to see if anyone can help me find a better example for the cron resource's command attribute.

James


From: goblin [notifications@github.com]
Sent: Thursday, March 21, 2013 1:20 PM
To: opscode/chef-docs
Cc: James Scott
Subject: Re: [chef-docs] cron: minor fixes (#50)

Thanks, that "merge" commit was me trying to sync up digital-science's clone to upstream... everything on it should already be in opscode master.

This pullreq was basically about these 2 commits that you said you'll include - which is OK :-) thanks


Reply to this email directly or view it on GitHubhttps://github.com/opscode/chef-docs/pull/50#issuecomment-15262882.

Contributor

jamescott commented Mar 21, 2013

OK. Some examples (quickly published), but hopefully they help provide more insight into what the command attribute can do within the context of the cron resource.

http://docs.opscode.com/resource_cron.html

James


From: James Scott
Sent: Thursday, March 21, 2013 1:55 PM
To: opscode/chef-docs
Subject: RE: [chef-docs] cron: minor fixes (#50)

Cool!

Thanks for the pull requests. I am asking around to see if anyone can help me find a better example for the cron resource's command attribute.

James


From: goblin [notifications@github.com]
Sent: Thursday, March 21, 2013 1:20 PM
To: opscode/chef-docs
Cc: James Scott
Subject: Re: [chef-docs] cron: minor fixes (#50)

Thanks, that "merge" commit was me trying to sync up digital-science's clone to upstream... everything on it should already be in opscode master.

This pullreq was basically about these 2 commits that you said you'll include - which is OK :-) thanks


Reply to this email directly or view it on GitHubhttps://github.com/opscode/chef-docs/pull/50#issuecomment-15262882.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment