Skip to content

Conversation

@david-cho-lerat-HL2
Copy link
Contributor

No description provided.

@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

@nik9000 nik9000 added the >docs General docs changes label May 30, 2017
@nik9000
Copy link
Member

nik9000 commented May 30, 2017

Thanks for opening this and the last one!

If possible, can you make these against the docs for 5.4? We don't tend to backport docs fixes beyond the current active branches so merging into 5.1 is kind of against policy. I did it for the last one because I figured it'd be ok but since you've opened another I'd like to get it pointed in a more "normal" place.

I honestly don't know if it is a good policy not to backport docs changes as far back as they go, but it is our current policy.

@david-cho-lerat-HL2
Copy link
Contributor Author

david-cho-lerat-HL2 commented May 30, 2017 via email

@nik9000
Copy link
Member

nik9000 commented May 30, 2017

Thanks for opening #24960!

@nik9000 nik9000 closed this May 30, 2017
@david-cho-lerat-HL2 david-cho-lerat-HL2 deleted the patch-3 branch May 30, 2017 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>docs General docs changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants