首先访问：https://github.com/gabrielecirulli/2048 然后fork出一个自己的版本
例如：https://github.com/zhuangbiaowei/2048
​
然后，在自己的机器上，执行：
git clone [email protected]:zhuangbiaowei/2048.git

    var merged = new Tile(positions.next, tile.value * 2);
    merged.mergedFrom = [tile, next];
​
    self.grid.insertTile(merged);
    self.grid.removeTile(tile);
​
    // Converge the two tiles' positions
    tile.updatePosition(positions.next);
​
    // Update the score
    self.score += merged.value;
​
    // The mighty 2048 tile
    if (merged.value === 2048) self.won = true;

    var pos =NameArray.indexOf(tile.value);
    var merged = new Tile(positions.next, NameArray[pos+1]);

    now_value=Math.pow(2,pos+2);
    self.score += now_value;
    if (now_value === 2048) self.won = true;

    var pos =NameArray.indexOf(tile.value);
    var tile_value=Math.pow(2,pos+1);
    //再修改一下刚才的那句：
    var classes = ["tile", "tile-" + tile_value, positionClass];

    .tile .tile-inner {
      border-radius: 3px;
      background: #eee4da;
      text-align: center;
      font-weight: bold;
      z-index: 10;
      font-size: 55px; }

http_proxy= git ls-remote http://internal-git-server/git/repo.git

$ http_proxy=bad_proxy no_proxy=* git ls-remote http://internal-git-server/git/repo.git
fatal: unable to access 'http://internal-git-server/git/repo.git/': Couldn't resolve proxy 'bad_proxy'

$ git checkout v2.7.0
$ make -j8 && make install # 我的工作站是四核CPU，故此使用 -j8 两倍并发执行编译

$ http_proxy=bad_proxy no_proxy=* git ls-remote http://internal-git-server/git/repo.git
206b4906c197e76fcc63d7a453f9e3aa00dfb3da        HEAD
206b4906c197e76fcc63d7a453f9e3aa00dfb3da        refs/heads/master

#!/bin/sh
​
make -j8 && make install && \
git --version && \
http_proxy=bad_proxy no_proxy=* \
git ls-remote http://internal-git-server/git/repo.git
​
case $? in
0)
    exit 0
    ;;
128)
    exit 1
    ;;
*)
    exit 128
    ;;
esac

$ git bisect run sh git-proxy-bug-test.sh

372370f1675c2b935fb703665358dd5567641107 is the first bad commit
commit 372370f1675c2b935fb703665358dd5567641107
Author: Knut Franke <[email protected]>
Date:   Tue Jan 26 13:02:48 2016 +0000
​
    http: use credential API to handle proxy authentication
​
    Currently, the only way to pass proxy credentials to curl is by including them
    in the proxy URL. Usually, this means they will end up on disk unencrypted, one
    way or another (by inclusion in ~/.gitconfig, shell profile or history). Since
    proxy authentication often uses a domain user, credentials can be security
    sensitive; therefore, a safer way of passing credentials is desirable.
​
    If the configured proxy contains a username but not a password, query the
    credential API for one. Also, make sure we approve/reject proxy credentials
    properly.
​
    For consistency reasons, add parsing of http_proxy/https_proxy/all_proxy
    environment variables, which would otherwise be evaluated as a fallback by curl.
    Without this, we would have different semantics for git configuration and
    environment variables.
​
    Helped-by: Junio C Hamano <[email protected]>
    Helped-by: Eric Sunshine <[email protected]>
    Helped-by: Elia Pinto <[email protected]>
    Signed-off-by: Knut Franke <[email protected]>
    Signed-off-by: Elia Pinto <[email protected]>
    Signed-off-by: Junio C Hamano <[email protected]>
​
:040000 040000 de69688dd93e4466c11726157bd2f93e47e67330 d19d021e8d1c2a296b521414112be0966bd9f09a M      Documentation
:100644 100644 f46bfc43f9e5e8073563be853744262a1bb4c5d6 dfc53c1e2554e76126459d6cb1f098facac28593 M      http.c
:100644 100644 4f97b60b5c8abdf5ab0610382a6d6fa289df2605 f83cfa686823728587b2a803c3e84a8cd4669220 M      http.h
二分查找运行成功

$ git show --oneline --stat 372370f1675c2b935fb703665358dd5567641107
372370f http: use credential API to handle proxy authentication
 Documentation/config.txt | 10 +++++--
 http.c                   | 77 ++++++++++++++++++++++++++++++++++++++++++++++++
 http.h                   |  1 +
 3 files changed, 85 insertions(+), 3 deletions(-)

01  diff --git a/http.c b/http.c
02  index 1d5e3bb..69da445 100644
03  --- a/http.c
04  +++ b/http.c
05  @@ -70,6 +70,7 @@ static long curl_low_speed_limit = -1;
06   static long curl_low_speed_time = -1;
07   static int curl_ftp_no_epsv;
08   static const char *curl_http_proxy;
09  +static const char *curl_no_proxy;
10   static const char *http_proxy_authmethod;
12   static struct {
13       const char *name;
13  @@ -624,6 +625,11 @@ static CURL *get_curl_handle(void)
15           }
16
17           curl_easy_setopt(result, CURLOPT_PROXY, proxy_auth.host);
18  +#if LIBCURL_VERSION_NUM >= 0x071304
19  +        var_override(&curl_no_proxy, getenv("NO_PROXY"));
20  +        var_override(&curl_no_proxy, getenv("no_proxy"));
21  +        curl_easy_setopt(result, CURLOPT_NOPROXY, curl_no_proxy);
22  +#endif
23       }
24       init_curl_proxy_auth(result);
25
26  --
27  2.8.0.rc0

http: honor no_http env variable to bypass proxy
​
Curl and its families honor several proxy related environment variables:
​
* http_proxy and https_proxy define proxy for http/https connections.
* no_proxy (a comma separated hosts) defines hosts bypass the proxy.
​
This command will bypass the bad-proxy and connect to the host directly:
​
    no_proxy=* https_proxy=http://bad-proxy/ \
    curl -sk https://google.com/
​
Before commit 372370f (http: use credential API to handle proxy auth...),
Environment variable "no_proxy" will take effect if the config variable
"http.proxy" is not set.  So the following comamnd won't fail if not
behind a firewall.
​
    no_proxy=* https_proxy=http://bad-proxy/ \
    git ls-remote https://github.com/git/git
​
But commit 372370f not only read git config variable "http.proxy", but
also read "http_proxy" and "https_proxy" environment variables, and set
the curl option using:
​
    curl_easy_setopt(result, CURLOPT_PROXY, proxy_auth.host);
​
This caused "no_proxy" environment variable not working any more.
​
Set extra curl option "CURLOPT_NOPROXY" will fix this.
​
Signed-off-by: Jiang Xin <[email protected]>