summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorKubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com>2016-11-28 11:45:09 -0800
committerGitHub <noreply@github.com>2016-11-28 11:45:09 -0800
commit3c9ada36060e01f732ce21fdede63ccf2a75eebd (patch)
tree639ddb35e840bf7fd53e48cfa330cfdf6c5bb234 /scripts
parent6fbd7a74a159dc83ca8eebf0f2b868fc6e09e7a9 (diff)
parent19c2fcbabd186da4097368393a4b1771feed31ee (diff)
Merge pull request #37478 from YuPengZTE/devMD037
Automatic merge from submit-queue fix the mistake type <!-- Thanks for sending a pull request! Here are some tips for you: 1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md 2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md 3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes --> **What this PR does / why we need it**: **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # **Special notes for your reviewer**: **Release note**: <!-- Steps to write your release note: 1. Use the release-note-* labels to set the release note state (if you have access) 2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. --> ```release-note ``` Signed-off-by: yupeng <yu.peng36@zte.com.cn>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions