Question

Closed. This question is seeking recommendations for books, tools, software libraries, and more. It does not meet Stack Overflow guidelines. It is not currently accepting answers.

我们不准许对书籍、工具、软件图书馆以及更多的图书馆征求建议的问题。你可以ed问这个问题,以便用事实和引言回答。

Closed 8 years ago.

Improve this question

我正在向一批开发商提出it,我发现 g是令人惊讶的工具。它也很难理解,因为理解格言要求了解好像的历史和观众工具本身。

是否有任何人很好地提到像“原始指南”这样的东西?

Answer 1

我从未看到过任何具体的东西。从“如何发挥作用”的角度来看,这里是一纸空文。了解一切背后(或至少大致相等)的指挥系统有助于学会更方便地使用指挥系统工具,并表明你在什么地方寻找文件,以更好地了解 g!

File menu

这在过去几个主要版本中有所变化——我说的是目前的状况。

更新和重载: 这也许是最令人困惑的事情。重载重整,因为如果你以同一个组合启动该方案的话。也就是说,如果某个部门被拆除/重新设立,如果一些承诺现在 d,你不会再看到。而另一方面,最新情况则更新了所有信息,但仍然显示以前显示的所有承诺。如果你重新调整基础,并希望确保你放弃我的话,这是一件好事——你可以看到原始版本和重新版。
参考资料:非常明显。参考资料包括标签和分支(可能很偏远)。你可以重新阅读,并列出点击某个人,以在历史上显示。

Views

如man page ,gitktake rel=“noreferer”>git-rev-list 帮助具体说明历史的备选办法。也可在“观点”菜单中相互确定。男子网页是找到更多信息,了解你如何控制看法的极好场所(主要在限制部分)。如果你先看<条码>git-log,你就看到其中很多。

Help

这里有一份主要的约束力清单。页: 1

Context menu

这体现了几个常见的孔隙孔孔孔波拉宁指挥系统,通常采用一种通用/过失行动方式。列入名单至少有助于你找到正确文件,了解他们所做的工作,如果你已经这样做的话。

git-diff (Diff this <-> selected
git-format-patch (make patch)
git-tag (create tag)
git-diff-tree (write commit to file, rarely used)
git-branch
git-cherry-pick
git-reset (reset branch to here) This prompts you for soft, mixed, or hard, with a brief reminder of what each does. Longer description on the man page, but of course you have to understand the concept of the index to really get it.

此时此刻,“承诺”和相关指挥应是自我解释的。

在分支机构的菜单方面,我们有git-checkout 。缩略语

Middle section

SHA1 ID: the hash of the current commitments. 复制/铺设一个终点站,就某个特定承诺采取行动,你用电箱找到。你们也可以在这里 past。

前线/后 but,增长号......显而易见!

Find! 这里的备选办法是完全的自我解释,但对于每个人的教育来说,这些选择类似于 git-log参数:“含有”是-grep,“touching paths”是论点,加上/removing string是<>-S。

Message/diff pane

这里,我们有承诺信息,还有电离层输出,例如使用<条码>git-log-p,略微增加:

“Branches”相当于git Branch -a --contains=<commit>。
“前言”/“后继”等于git 描述[-contains] <commit> (git-dereg )

Answer 2

这里是用屏幕显示器对分支历史的直观介绍。

http://lostechies.com/joshuaflanagan/09/03/use-gitk-to-understand-git/

The upper left pane shows the series of commits to this repository, with the most recent on top.

There have been three commits, all by Tony Stark.

The commit message for the most recent commit was “third commit”

There is a single local branch, named “master’”, it points to the most recent commit

There is a single remote reference branch: the “master” branch from the remote repository named “origin”, it also points to the most recent commit

The yellow dot next to the top commit indicates that is the snapshot currently in my working folder (referred to as HEAD)

I’ve highlighted the second commit, so that I can see its details in the lower pane

The commit SHA (unique identifier, similar to subversion revision number) of the second commit is
3d024dd9e4a83d8c6a9a143a68b75d4b872115a6

The lower right shows the list of files impacted by the second commit

The lower left shows the commit details, including the full diff

Clicking a file in the lower right pane scrolls the diff in the lower left pane to the corresponding section 12.

Answer 3

在“ g树和历史的结合”方面,可以真正使用什么子,这是如何通过审视 g树观点来认识所发生的事情的具体解释。

就我而言,看树木的正确途径是(当然):

 1. each node is a commit
 2. ultimate parent is at the bottom
 3. direct child to a commit is the one that happened first in the same branch (no matter who did it)
 4. the node with 2 or more children indicates ... ?
 5. merge commit node has 2 parents.
 6. rebase is recognized ... ?

还要感谢放映。

树木实际上代表了存放地的现状。如果我们能够通过审视树木观点来说明所发生的情况,那将是巨大的。

增编

页: 1

Answer 4

我认为,对“金库”接口唯一有用的是冰(col)分行概览。