重定向
A little understanding of how *nix pipes work would help.
In short the '>>' pipe operator will append lines to the end of the specified file,
where-as the single greater than '>' will empty and overwrite the file.
>清空文件,再写入
>>追加
How to get git producing output to a file?
Thanks for your help!
I just have found the solution:
Part 1
(Thanks to the answer of dessert)git
by design does never write to stdout
but stderr
. So I needed to redirect stderr
, too, in order to get the output using
git clone XYZ &> git_clone.file
Part 2
Anyway this wasn't enough and I only received the "uninteresting" part of the output to the file but not the lines of the progress I really wanted.
Doing further reserach again in man git-clone
I realized there exists an option
--progress
progress status is reported on the standard error stream by
default when it is attached to a terminal, unless -q is
specified. This flag forces progress status even if the standard
error stream is not directed to a terminal.
Though I'ld think it actually was already attached to a terminal, this now seems to force git to write the lines of the progress part I'm most interested in finally to stderr
as well so I can now get them using
git clone --progress XYZ &> git_clone.file
自己使用的命令
ssh -o SendEnv=GIT_PROTOCOL git@github.com -v -v -v -v &> ssh-debug.log
作者:Chuck Lu GitHub |
【推荐】国内首个AI IDE,深度理解中文开发场景,立即下载体验Trae
【推荐】编程新体验,更懂你的AI,立即体验豆包MarsCode编程助手
【推荐】抖音旗下AI助手豆包,你的智能百科全书,全免费不限次数
【推荐】轻量又高性能的 SSH 工具 IShell:AI 加持,快人一步
· 记一次.NET内存居高不下排查解决与启示
· 探究高空视频全景AR技术的实现原理
· 理解Rust引用及其生命周期标识(上)
· 浏览器原生「磁吸」效果!Anchor Positioning 锚点定位神器解析
· 没有源码,如何修改代码逻辑?
· 全程不用写代码,我用AI程序员写了一个飞机大战
· DeepSeek 开源周回顾「GitHub 热点速览」
· MongoDB 8.0这个新功能碉堡了,比商业数据库还牛
· 记一次.NET内存居高不下排查解决与启示
· 白话解读 Dapr 1.15:你的「微服务管家」又秀新绝活了