logger.xorm.MODE : ,: “xorm” 记录器 ACCESS_LOG_TEMPLATE : {{.Ctx.RemoteHost}} - {{.Identity}} {{.Start.Format "[02/Jan/2006:15:04:05 -0700]" }} " {{.Ctx.Req.Method}} {{.Ctx.Req.URL.RequestURI}} {{.Ctx.Req.Proto}}" WARN 或更高级别将导致 不记录访问日志。 此值表示一个 Go 模板。其默认值为 1. {{.Ctx.RemoteHost}} - {{.Identity}} {{.Start.Format "[02/Jan/2006:15:04:05 -0700]" }} "{{.Ctx.Req.Method}} {{.Ctx.Req.URL.RequestURI}} {{.Ctx.Req.Proto}}" https://gitea.example.com/api/packages/{owner}/nuget/symbols 参数 描述 owner 软件包注册表的所有者 例如： 1. https://gitea.example.com/api/packages/testuser/nuget/symbols 要从软件包注册表安装 NuGet 软件包，请执行以下命令： 1. dotnet add package

blame git grep Patching git cherry-pick git rebase git revert Email git apply git am git format-patch git imap-send git send-email git request-pull External Systems git svn git fast-import computers today. RCS works by keeping patch sets (that is, the differences between files) in a special format on disk; it can then re-create what any file looked like at any point in time by adding up all of commits. In addition, the short, full, and fuller values show the output in roughly the same format but with less or more information, respectively: $ git log --pretty=oneline ca82a6dff817ec66f4

computers today. RCS works by keeping patch sets (that is, the differences between files) in a special format on disk; it can then re-create what any file looked like at any point in time by adding up all the of commits. In addition, the short, full, and fuller values show the output in roughly the same format but with less or more information, respectively: $ git log --pretty=oneline ca82a6dff817ec66f4 option value is format, which allows you to specify your own log output format. This is especially useful when you’re generating output for machine parsing — because you specify the format explicitly, you

blame git grep Patching git cherry-pick git rebase git revert Email git apply git am git format-patch git imap-send git send-email git request-pull External Systems git svn git fast-import computers today. RCS works by keeping patch sets (that is, the differences between files) in a special format on disk; it can then re-create what any file looked like at any point in time by adding up all of commits. In addition, the short, full, and fuller values show the output in roughly the same format but with less or more information, respectively: $ git log --pretty=oneline ca82a6dff817ec66f4

a11bef06a3f659402fe7563abf99ad00de2209e6 first commit 最有意思的是 format ，可以定制记录的显示格式。 这样的输出对后期提取分析格外有用——因为你知道输出的 格式不会随着 Git 的更新而发生改变： 46 $ git log --pretty=format:"%h - %an, %ar : %s" ca82a6d - Scott Chacon, 6 years a11bef0 - Scott Chacon, 6 years ago : first commit git log --pretty=format 常用的选项 列出了 format 接受的常用格式占位符的写法及其代表的意义。 表格 2. git log --pretty=format 常用的选项 选项 说明 %H 提交的完整哈希值 %h 提交的简写哈希值 %T 树的完整哈希值 %t 树的简写哈希值 作者，而那个核心成员就是提交者。 我们会在 分布式 Git 再详细介绍两者之间的细微差别。 当 oneline 或 format 与另一个 log 选项 --graph 结合使用时尤其有用。 这个选项添加了一些 ASCII 字符串 来形象地展示你的分支、合并历史： 47 $ git log --pretty=format:"%h %s" --graph * 2d3acf9 ignore errors from SIGCHLD

bisect git blame git grep 补丁 git cherry-pick git rebase git revert 邮件 git apply git am git format-patch git imap-send git send-email git request-pull 外部系统 git svn git fast-import 管理 git gc a11bef06a3f659402fe7563abf99ad00de2209e6 first commit 最有意思的是 format ，可以定制记录的显示格式。 这样的输出对后期提取分 析格外有用——因为你知道输出的格式不会随着 Git 的更新而发生改变： $ git log --pretty=format:"%h - %an, %ar : %s" ca82a6d - Scott Chacon, 6 years - Scott Chacon, 6 years ago : first commit git log --pretty=format 常用的选项 列出了 format 接受的常用格式占位符 的写法及其代表的意义。 表格 2. git log --pretty=format 常用的选项 选项 说明 %H 提交的完整哈希值 %h 提交的简写哈希值 %T 树的完整哈希值 %t 树的简写哈希值