they’re clever). This approach is very common because it is so simple, but it is also incredibly error prone. It is easy to forget which directory you’re in and accidentally write to the wrong file or isn’t merged in yet, trying to delete it with git branch -d will fail: $ git branch -d testing error: The branch 'testing' is not fully merged. If you are sure you want to delete it, run 'git branch an issue (iss91), working on it for a bit, branching off the second branch to try another way of handling the same thing (iss91v2), going back to your master branch and working there for a while, and then

they’re clever). This approach is very common because it is so simple, but it is also incredibly error prone. It is easy to forget which directory you’re in and accidentally write to the wrong file or isn’t merged in yet, trying to delete it with git branch -d will fail: $ git branch -d testing error: The branch 'testing' is not fully merged. If you are sure you want to delete it, run 'git branch an issue (iss91), working on it for a bit, branching off the second branch to try another way of handling the same thing ( iss91v2), going back to your master branch and working there for a while, and

they’re clever). This approach is very common because it is so simple, but it is also incredibly error prone. It is easy to forget which directory you’re in and accidentally write to the wrong file or isn’t merged in yet, trying to delete it with git branch -d will fail: $ git branch -d testing error: The branch 'testing' is not fully merged. If you are sure you want to delete it, run 'git branch an issue (iss91), working on it for a bit, branching off the second branch to try another way of handling the same thing (iss91v2), going back to your master branch and working there for a while, and then

--no-merged testing 这里显示了其他分支。 因为它包含了还未合并的工作，尝试使用 git branch -d 命令删除它时会失败： $ git branch -d testing error: The branch 'testing' is not fully merged. If you are sure you want to delete it, run 'git branch origin master To john@githost:simplegit.git ! [rejected] master -> master (non-fast forward) error: failed to push some refs to 'john@githost:simplegit.git' 这时 John 会推送失败，因为之前 Jessica 已经推送了她的更改。 如果之前习惯于用 apply --check 命令： $ git apply --check 0001-seeing-if-this-helps-the-gem.patch error: patch failed: ticgit.gemspec:1 error: ticgit.gemspec: patch does not apply 如果没有产生输出，则该补丁可以顺利应用。 如果检查失败了，该命令还会以一个非零的状态退出，所以需要

--no-merged testing 这里显示了其他分支。 因为它包含了还未合并的工作，尝试使用 git branch -d 命令删除它时会失败： $ git branch -d testing error: The branch 'testing' is not fully merged. If you are sure you want to delete it, run 'git branch origin master To john@githost:simplegit.git ! [rejected] master -> master (non-fast forward) error: failed to push some refs to 'john@githost:simplegit.git' 这时 John 会推送失败，因为之前 Jessica 已经推送了她的更改。 如果之前习 apply --check 命令： $ git apply --check 0001-seeing-if-this-helps-the-gem.patch error: patch failed: ticgit.gemspec:1 error: ticgit.gemspec: patch does not apply 如果没有产生输出，则该补丁可以顺利应用。 如果检查失败了，该命令还会 以一个

的日志子部分中配置每个 模式。 \[log.writer-mode-name\] . LEVEL : Info: 日志级别。可选值：[Trace, Debug, Info, Warn, Error, Critical, Fatal, 项目 ( project ) 工单和合并请求的附件 ( attachment ) 日志 ( log ) 配置说明 - 108 - 本文档使用 书栈网 构建 None] STACKTRACE_LEVEL : None: 记录创建堆栈跟踪的默认日志级别（很少有用，不要设置它）。可选值：[Trace, Debug, Info, Warn, Error, Critical, Fatal, None] ENABLE_SSH_LOG : false: 将 SSH 日志保存到日志文件中。 logger.access.MODE : empty: 记录器的日志输出列表。 LEVEL ：（默认值：Info）：要持久化的最严重的日志事件，不区分大小写。可能的值 为： Trace 、 Debug 、 Info 、 Warn 、 Error 、 Fatal 。 STACKTRACE_LEVEL ：（默认值：None）：对于此类及更严重的事件，将在记录时打印堆栈跟踪。 它还可以包含以下子日志记录器： logger.router