Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
git
提交
0040d6eb
G
git
项目概览
李少辉-开发者
/
git
与 Fork 源项目一致
从无法访问的项目Fork
通知
2
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
git
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
0040d6eb
编写于
10月 30, 2013
作者:
J
Junio C Hamano
浏览文件
操作
浏览文件
下载
差异文件
Merge branch 'tr/gitk-doc-update'
* tr/gitk-doc-update: Documentation: revamp gitk(1)
上级
832ee79a
744db23c
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
83 addition
and
24 deletion
+83
-24
Documentation/gitk.txt
Documentation/gitk.txt
+83
-24
未找到文件。
Documentation/gitk.txt
浏览文件 @
0040d6eb
...
...
@@ -8,7 +8,7 @@ gitk - The Git repository browser
SYNOPSIS
--------
[verse]
'gitk' [<option
>...] [<revs>] [
--] [<path>...]
'gitk' [<option
s>] [<revision range>] [\
--] [<path>...]
DESCRIPTION
-----------
...
...
@@ -16,21 +16,38 @@ Displays changes in a repository or a selected set of commits. This includes
visualizing the commit graph, showing information related to each commit, and
the files in the trees of each revision.
Historically, gitk was the first repository browser. It's written in tcl/tk
and started off in a separate repository but was later merged into the main
Git repository.
OPTIONS
-------
To control which revisions to show, the command takes options applicable to
the 'git rev-list' command (see linkgit:git-rev-list[1]).
This manual page describes only the most
frequently used options.
-n <number>::
--max-count=<number>::
To control which revisions to show, gitk supports most options
applicable to the 'git rev-list' command. It also supports a few
options applicable to the 'git diff-*' commands to control how the
changes each commit introduces are shown. Finally, it supports some
gitk-specific options.
gitk generally only understands options with arguments in the
'sticked' form (see linkgit:gitcli[7]) due to limitations in the
command line parser.
rev-list options and arguments
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This manual page describes only the most frequently used options. See
linkgit:git-rev-list[1] for a complete list.
--all::
Show all refs (branches, tags, etc.).
Limits the number of commits to show.
--branches[=<pattern>]::
--tags[=<pattern>]::
--remotes[=<pattern>]::
Pretend as if all the branches (tags, remote branches, resp.)
are listed on the command line as '<commit>'. If '<pattern>'
is given, limit refs to ones matching given shell glob. If
pattern lacks '?', '{asterisk}', or '[', '/{asterisk}' at the
end is implied.
--since=<date>::
...
...
@@ -40,9 +57,9 @@ frequently used options.
Show commits older than a specific date.
--
all
::
--
date-order
::
S
how all branches
.
S
ort commits by date when possible
.
--merge::
...
...
@@ -51,19 +68,37 @@ frequently used options.
that modify the conflicted files and do not exist on all the heads
being merged.
--argscmd=<command>::
Command to be run each time gitk has to determine the list of
<revs> to show. The command is expected to print on its standard
output a list of additional revs to be shown, one per line.
Use this instead of explicitly specifying <revs> if the set of
commits to show may vary between refreshes.
--left-right::
--select-commit=<ref>::
Mark which side of a symmetric diff a commit is reachable
from. Commits from the left side are prefixed with a `<`
symbol and those from the right with a `>` symbol.
Automatically select the specified commit after loading the graph.
Default behavior is equivalent to specifying '--select-commit=HEAD'.
--full-history::
When filtering history with '<path>...', does not prune some
history. (See "History simplification" in linkgit:git-log[1]
for a more detailed explanation.)
--simplify-merges::
<revs>::
Additional option to '--full-history' to remove some needless
merges from the resulting history, as there are no selected
commits contributing to this merge. (See "History
simplification" in linkgit:git-log[1] for a more detailed
explanation.)
--ancestry-path::
When given a range of commits to display
(e.g. 'commit1..commit2' or 'commit2 {caret}commit1'), only
display commits that exist directly on the ancestry chain
between the 'commit1' and 'commit2', i.e. commits that are
both descendants of 'commit1', and ancestors of 'commit2'.
(See "History simplification" in linkgit:git-log[1] for a more
detailed explanation.)
<revision range>::
Limit the revisions to show. This can be either a single revision
meaning show from the given revision and back, or it can be a range in
...
...
@@ -78,6 +113,23 @@ frequently used options.
avoid ambiguity with respect to revision names use "--" to separate the paths
from any preceding options.
gitk-specific options
~~~~~~~~~~~~~~~~~~~~~
--argscmd=<command>::
Command to be run each time gitk has to determine the revision
range to show. The command is expected to print on its
standard output a list of additional revisions to be shown,
one per line. Use this instead of explicitly specifying a
'<revision range>' if the set of commits to show may vary
between refreshes.
--select-commit=<ref>::
Select the specified commit after loading the graph.
Default behavior is equivalent to specifying '--select-commit=HEAD'.
Examples
--------
gitk v2.6.12.. include/scsi drivers/scsi::
...
...
@@ -101,6 +153,13 @@ Files
Gitk creates the .gitk file in your $HOME directory to store preferences
such as display options, font, and colors.
History
-------
Gitk was the first graphical repository browser. It's written in
tcl/tk and started off in a separate repository but was later merged
into the main Git repository.
SEE ALSO
--------
'qgit(1)'::
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录