Skip to content

Conversation

@abhi
Copy link
Contributor

@abhi abhi commented Oct 4, 2017

Since cherry pick fails due to code reorg, I have manually updated the respective files.
(cherry picked from commit fe0d7f6)
(cherry picked from commit ed271d4)

@codecov
Copy link

codecov bot commented Oct 4, 2017

Codecov Report

Merging #2394 into bump_v17.06 will increase coverage by <.01%.
The diff coverage is 100%.

@@               Coverage Diff               @@
##           bump_v17.06    #2394      +/-   ##
===============================================
+ Coverage        59.75%   59.76%   +<.01%     
===============================================
  Files              120      120              
  Lines            25067    25093      +26     
===============================================
+ Hits             14980    14998      +18     
- Misses            8754     8759       +5     
- Partials          1333     1336       +3

Copy link
Contributor

@nishanttotla nishanttotla left a comment

Choose a reason for hiding this comment

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

@abhi just a small quick thing: Can you refer to the two commits from #2324, so that the commit message looks somewhat like a cherry pick? It'll be useful to track back later.

@abhi
Copy link
Contributor Author

abhi commented Oct 4, 2017

@nishanttotla done.

@nishanttotla
Copy link
Contributor

@abhi I actually meant that the commit hashes should go into the commit message, not just PR description. Something like
(cherry picked from commit fe0d7f63cd93f9cb65c8533393a1447f4f55c63c)
(cherry picked from commit ed271d4ae37d782f53d70f04535850239aff2722)

Copy link
Contributor

@nishanttotla nishanttotla left a comment

Choose a reason for hiding this comment

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

LGTM once commit message is updated.

Ping @dperny @anshulpundir

@abhi
Copy link
Contributor Author

abhi commented Oct 4, 2017

Please do not merge yet. I might need to update libnetwork vendoring due to a last minute change going in.

@nishanttotla
Copy link
Contributor

@abhi can the libnetwork update be done in a separate cherry pick if it indeed is required?

@abhi
Copy link
Contributor Author

abhi commented Oct 4, 2017

@nishanttotla unfortunately no. I guess release branch needs to have consistent vendoring. PR moby/libnetwork#1970 is reverting a change in the bump_17.06 branch. So we might need to honor it.

Signed-off-by: Abhinandan Prativadi <abhi@docker.com>
@dperny
Copy link
Collaborator

dperny commented Oct 5, 2017

LGTM

@dperny dperny merged commit 8afb0c4 into moby:bump_v17.06 Oct 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants