From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Date: Fri, 18 Feb 2011 00:36:31 +0000 (+0000)
Subject: Don't propagate information about ut_holepunch over PEX.
X-Git-Tag: 2.30b1~317
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e35d1aacafac2bc618de2efa66422cfaf563d795;p=transmission

Don't propagate information about ut_holepunch over PEX.

It's not useful, says Greg.
---

diff --git a/libtransmission/peer-msgs.c b/libtransmission/peer-msgs.c
index 73cbb9012..826682bc4 100644
--- a/libtransmission/peer-msgs.c
+++ b/libtransmission/peer-msgs.c
@@ -939,12 +939,6 @@ parseLtepHandshake( tr_peermsgs *     msgs,
             msgs->ut_metadata_id = (uint8_t) i;
             dbgmsg( msgs, "msgs->ut_metadata_id is %d", (int)msgs->ut_metadata_id );
         }
-        /* We don't support ut_holepunch yet, but we might as well
-           propagate this information over PEX. */
-        if( tr_bencDictFindInt( sub, "ut_holepunch", &i ) ) {
-            if( i != 0 )
-                pex.flags |= ADDED_F_HOLEPUNCH;
-        }
     }
 
     /* look for metainfo size (BEP 9) */