tree 73ce441060de5f5e063f197cf98da84d1baea8e1
parent a541643986dd89967d77719b4b9d7e5401be3302
author Jonathan Nieder <jrn@google.com> 1508973798 -0700
committer Gerrit Code Review <noreply-gerritcodereview@google.com> 1508973219 +0000

Update git submodules

* Update plugins/download-commands from branch 'master'
  - Merge branch 'stable-2.15'
    
    * stable-2.15:
      CloneWithCommitMsgHook: Stop passing --insecure to curl
    
    Change-Id: I16b388db6a5d36b8a60d9c9ab09d9a793bad24a2
    
  - Merge branch 'stable-2.14' into stable-2.15
    
    * stable-2.14:
      CloneWithCommitMsgHook: Stop passing --insecure to curl
    
    Change-Id: I4ff216985885be55959a79f430ee1894fb5ba1d7
    
  - CloneWithCommitMsgHook: Stop passing --insecure to curl
    
    Validating certs is an important feature of HTTPS that we should not
    disable, especially when downloading code that is going to be trusted.
    
    This "curl" invocation does not take place until after a successful
    "git clone", so the -k option would not be useful for dealing with
    misconfigured https servers.  Any configuration that needs -k would
    already be broken because of the "git clone" that comes before it.
    
    Reported-by: Gert van Dijk <gertvdijk@gmail.com>
    Bug: Issue 7562
    Change-Id: Ibe14bba5c1ce30a771515ff7985796aa1b8cdadf