zhanhailiang 日期:2015-01-07
The direct use of the command line git pull operation is normal, as follows:
d:\vipshop\mstats\mstats-monitor>git pullupdating 5050c42. E8b3bd9fast-forward Public/css/app.css | ++++++++++++++++++ Public/js/page.counts.js | +++++++++++++++++++++++++++++++++--------views/counts.html | 8 +++++ views/includes/module_list.html | 3 + 4 files changed, insertions (+), deletions (-)
but using tortoisegit pull times wrong"/bin/sed:bad file number ", the details are as follows:
git.exe pull-v--progress" origin "/libexec/git-core/git-sh-setup:line Bayi:/bin/sed:bad fi Le numberfrom http://gitlab.tools.vipshop.com/wade.zhan/mstats-monitor= [up to date] master, Origin/masterc: \program Files (x86) \git/libexec/git-core\git-pull:line 268:/bin/tr:bad file Numberyour configuration Specifies to Merg E with the ref ' master ' from the remote, but no such ref is fetched.git did not exit cleanly (exit code 1) (2090 MS @ 2015 /1/7 10:08:05)
According to the tip "Your configuration specifies to merge with the ref ' master ' from the remote, but no such ref is fetched.", referring to the merge far end References master, but does not fetch the reference.
Check out the git help pull command details:
git pull [options] [<repository> [<refspec>…]]
The suspect is caused by a lack of parameters, try to execute the full command manually, as follows:
d:\vipshop\mstats\mstats-monitor>git.exe pull-v--progress" origin "MasterFrom Http://gi Tlab.tools.vipshop.com/wade.zhan/mstats-monitor * Branch Master, Fetch_head = [up to date] Master Origin/masteralready up-to-date.
Here is the problem, should be caused by default parameters, the right-click menu Tortoisegit->settings->git->edit Local git/config, in [branch "master"] Modify remote = Origin master, such as:
The Tortoisegit pull can then be used normally:
git.exe pull -v --progress "origin" masterFrom http://gitlab.tools.vipshop.com/wade.zhan/mstats-monitor* branch master -> FETCH_HEAD= [up to date] master -> origin/masterAlready up-to-date.Success (2121 ms @ 2015/1/7 10:08:38)
Reference article:
- http://blog.csdn.net/renfufei/article/details/41648061
Tortoisegit Bad file number workaround