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

[#4154] Wrong "make collect" statement documented instead of "make update" when documentation should be regenerated #4155

Merged
merged 1 commit into from
May 1, 2017

Conversation

christiangalsterer
Copy link
Contributor

No description provided.

…make update" when documentation should be regenerated
@elasticmachine
Copy link
Collaborator

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run.

1 similar comment
@elasticmachine
Copy link
Collaborator

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run.

Copy link
Contributor

@ruflin ruflin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@christiangalsterer Thanks for the fix. Missed to update this doc line when I changed it to make update :-(

@ruflin
Copy link
Contributor

ruflin commented May 1, 2017

jenkins, test it

@ruflin ruflin merged commit 4cec36a into elastic:master May 1, 2017
@dedemorton
Copy link
Contributor

@ruflin Does this need to be backported? If so, which releases?

@ruflin
Copy link
Contributor

ruflin commented May 3, 2017

I think it applies to all releases >= 5.1. But backporting it to 5.4 and 5.x should be enough I hope?

dedemorton pushed a commit to dedemorton/beats that referenced this pull request May 6, 2017
…make update" when documentation should be regenerated (elastic#4155)
ruflin pushed a commit that referenced this pull request May 8, 2017
…date" when documentation should be regenerated (#4155)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants