-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Move release-1.2 forward to 3d58b9c07fdd2bf8cb063c30d791b94649b794e5 #22710
Conversation
for vsphere provider docker currently only supports 1.9.1 release. The older versions of docker are failing on jessie due to issue moby/moby#18793 and newer version 1.10.x is not properly tested.
All AWS errors should be wrapped in a user-friendly error before returning.
…se.sh Resolves issue kubernetes#22139
Configurations in config-default.sh should take default values if they are set outside of the script. `roles` option is an exception. This patch fix it to maintain consistency behavior with other options.
…w gcr image consistent with the code base. Change the label on the daemonset to 'app'.
I'm trying to figure out how to get a diffstat without the (obvious) docs nonsense... We'll see.... |
The diff of the PR I wanted to exclude is at the bottom. At a glance, the rest looks like doc-munging-related changes. |
GCE e2e build/test passed for commit 3eb6278. |
Diff from this PR to upstream master (3d58b9c) https://gist.github.com/eparis/591788686969412309e4 This diff ignores all changes to files which end in .md This is the rest.... |
I got that diff by adding the following to my .git/config
And then putting the following in /tmp/diff.sh #!/bin/bash
LOCAL="$1"
REMOTE="$2"
if [[ $LOCAL == *".md" ]]; then
exit
fi
diff -Naup -I 'releases.k8s.io' "${LOCAL}" "${REMOTE}" And running:
So now you can reproduce my results at home! (I am assuming that everyone will have my commit in their tree, in case you don't and are interested...) I have
So all I have to do is
|
Awesome. LGTM |
Can we include the reproduction steps here for history's sake? In case we need to do something like this in the future. Commands with comments, please. |
Notice this does not 'rewrite' history, it does not leave a vestigial tag, it just marches the release-1.2 branch forward. I hope people won't need to do this often. A wholesale update like this just doesn't belong. But basically what happened was the bgrant reviewed every PR between the release-1.2 branch (4d599ea) and master (3d58b9c) he indicated every commit between those 2 points was reasonable for 1.2 except possibly #22430. So I found the first commit before the problematic PR. That first commit was 7e9256b. So my basic steps (with a bit of pseudo-code)
|
Merging. |
Move release-1.2 forward to 3d58b9c
Move release-1.2 forward to 3d58b9c
Move release-1.2 forward to 3d58b9c
however this excludes PR #22430