Home
last modified time | relevance | path

Searched full:git (Results 1 – 25 of 388) sorted by relevance

12345678910>>...16

/linux/Documentation/admin-guide/
H A Dbug-bisect.rst8 This document describes how to use a ``git bisect`` to find the source code
25 This includes having a Git clone with the appropriate sources, installing the
31 * Preparation: start the bisection and tell Git about the points in the history
32 you consider to be working and broken, which Git calls 'good' and 'bad'::
34 git bisect start
35 git bisect good v6.0
36 git bisect bad v6.1
38 Instead of Git tags like 'v6.0' and 'v6.1' you can specify commit-ids, too.
41 needs of the codebase Git checked out for testing::
48 bisection a later change resolves. In such cases run ``git bisect skip`` and
[all …]
/linux/tools/perf/Documentation/
H A Dexamples.txt66 well. For example the page allocations done by a 'git gc' can be
69 titan:~/git> perf record -e kmem:mm_page_alloc -c 1 ./git gc
79 titan:~/git> perf report
85 23.57% git-repack /lib64/libc-2.5.so
86 21.81% git /lib64/libc-2.5.so
87 14.59% git ./git
88 11.79% git-repack ./git
89 7.12% git /lib64/ld-2.5.so
90 3.16% git-repack /lib64/libpthread-2.5.so
91 2.09% git-repack /bin/bash
[all …]
H A Dmanpage-base.xsl11 git.docbook.backslash and git.docbook.dot params
15 $git.docbook.backslash,'fB(',
17 $git.docbook.backslash,'fR')"/>
20 <xsl:value-of select="$git.docbook.dot"/>
27 $git.docbook.backslash,'fB',
29 '. ',$git.docbook.backslash,'fR')"/>
31 <xsl:value-of select="$git.docbook.dot"/>
/linux/Documentation/translations/zh_CN/admin-guide/
H A Dbug-bisect.rst34 使用 ``git`` 提供的工具可以很容易地找到缺陷，只要缺陷是可复现的。
41 $ git bisect start
45 $ git bisect bad [commit]
49 $ git bisect good [commit]
54 $ git bisect good
58 $ git bisect bad
61 - 在一些交互之后，git bisect将给出可能导致缺陷的变更集。
65 $ git bisect start
66 $ git bisect bad # Current version is bad
67 $ git bisect good v4.8
[all …]
/linux/
H A DMAINTAINERS32 Type is one of: git, hg, quilt, stgit, topgit
51 get_maintainer will not look at git log history when an F: pattern
52 match occurs. When an N: match occurs, git log history is used
53 to also notify the people that have git commit signatures.
117 T: git git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git
118 T: git git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git
142 T: git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
160 T: git git://git.kernel.org/pub/scm/linux/kernel/git/ericvh/v9fs.git
161 T: git git://github.com/martinetd/linux.git
290 T: git git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
[all …]
/linux/Documentation/translations/zh_TW/admin-guide/
H A Dbug-bisect.rst37 使用 ``git`` 提供的工具可以很容易地找到缺陷，只要缺陷是可復現的。
44 $ git bisect start
48 $ git bisect bad [commit]
52 $ git bisect good [commit]
57 $ git bisect good
61 $ git bisect bad
64 - 在一些交互之後，git bisect將給出可能導致缺陷的變更集。
68 $ git bisect start
69 $ git bisect bad # Current version is bad
70 $ git bisect good v4.8
[all …]
/linux/Documentation/process/
H A Dbackporting.rst30 Sometimes the patch you are backporting already exists as a git commit,
32 ``git cherry-pick``. However, if the patch comes from an email, as it
34 using ``git am``.
36 If you've ever used ``git am``, you probably already know that it is
43 destination tree, as this will make git output conflict markers and let
44 you resolve conflicts with the help of git and any other conflict
57 A good reason to prefer ``git cherry-pick`` over ``git am`` is that git
67 article will assume that you are doing a plain ``git cherry-pick``.
72 Once you have the patch in git, you can go ahead and cherry-pick it into
104 If your attempted cherry-pick fails with a conflict, git automatically
[all …]
H A D7.AdvancedTopics.rst11 Managing patches with git
20 BitKeeper. For better or for worse, the kernel project has settled on git
23 Managing patches with git can make life much easier for the developer,
24 especially as the volume of those patches grows. Git also has its rough
27 teach the reader how to use git; that would be sufficient material for a
28 long document in its own right. Instead, the focus here will be on how git
30 wish to come up to speed with git will find more information at:
32 https://git-scm.com/
34 https://www.kernel.org/pub/software/scm/git/docs/user-manual.html
39 understanding of how git works before trying to use it to make patches
[all …]
/linux/Documentation/translations/zh_CN/maintainer/
H A Dpull-requests.rst41 git tag -s char-misc-4.15-rc1 char-misc-next
44 的标记，并用您的gpg密钥签名（参见 Documentation/maintainer/configure-git.rst ）。
48 当您运行上述命令时 ``git`` 会打开编辑器要求你描述一下这个标记。在本例中您需要
111 git push origin char-misc-4.15-rc1
117 最后要做的是创建拉取请求消息。可以使用 ``git request-pull`` 命令让 ``git``
121 …git request-pull master git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ char-m…
127 git:// 协议拉取。如果你希望使用 https:// 协议，也可以用在这里（但是请
133 “git request-pull”会包含git树的地址和需要拉取的特定标记，以及标记
137 Linus回复说他倾向于 ``git://`` 协议。其他维护者可能有不同的偏好。另外，请注意
148 [GIT PULL] <subsystem> changes for v4.15-rc1
H A Dconfigure-git.rst3 :Original: Documentation/maintainer/configure-git.rst
17 GPG公钥进行签名。可以通过将 ``-u`` 标志传递给 ``git tag`` 来创建签名标记。
20 git config user.signingkey "keyname"
22 或者手动编辑你的 ``.git/config`` 或 ``~/.gitconfig`` 文件::
29 你可能需要告诉 ``git`` 去使用 ``gpg2``::
49 通过在git中添加以下钩子，可以将此配置为在发布 ``git am`` 时自动执行：
53 $ git config am.messageid true
54 $ cat >.git/hooks/applypatch-msg <<'EOF'
56 . git-sh-setup
62 $ chmod a+x .git/hooks/applypatch-msg
/linux/Documentation/translations/it_IT/process/
H A D7.AdvancedTopics.rst16 Gestire le modifiche con git
25 peggio, il progetto del kernel ha deciso di usare git per gestire i sorgenti.
27 Gestire le modifiche con git può rendere la vita dello sviluppatore molto
29 Git ha anche i suoi lati taglienti che possono essere pericolosi; è uno
32 di git ai suoi lettori; ci sarebbe materiale a sufficienza per un lungo
34 git è parte del processo di sviluppo del kernel. Gli sviluppatori che
35 desiderassero diventare agili con git troveranno più informazioni ai
38 https://git-scm.com/
40 https://www.kernel.org/pub/software/scm/git/docs/user-manual.html
46 base solida su come funziona git. Uno sviluppatore che sappia usare git
[all …]
/linux/scripts/
H A Dsetlocalversion5 # control system git.
39 if [ "$(git cat-file -t "$tag" 2> /dev/null)" != tag ]; then
45 set -- $(git rev-list --count --left-right "$tag"...HEAD 2> /dev/null)
48 # string comparison, because $1 is empty if the 'git rev-list'
77 if test -n "$(git rev-parse --show-cdup 2>/dev/null)"; then
81 if ! head=$(git rev-parse --verify HEAD 2>/dev/null); then
118 # running further git commands
141 # You cannot use 'git describe --dirty' because it tries to create
142 # .git/index.lock .
143 # First, with git-status, but --no-optional-locks is only supported in
[all …]
H A Dgit.orderFile3 # order file for git, to produce patches which are easier to review
7 # git diff -O scripts/git.orderFile ...
9 # add to git config:
10 # git config diff.orderFile scripts/git.orderFile
19 # git-specific
21 scripts/git.orderFile
H A Dobjdiff12 # $ git checkout COMMIT_A
16 # $ git checkout COMMIT_B
28 SRCTREE=$(cd $(git rev-parse --show-toplevel 2>/dev/null); pwd)
31 echo >&2 "ERROR: Not a git repository."
76 CMT="`git rev-parse --short HEAD`"
97 SRC="`git rev-parse --short HEAD^`"
98 DST="`git rev-parse --short HEAD`"
100 SRC="`git rev-parse --short $1`"
101 DST="`git rev-parse --short $2`"
133 CMT="`git rev-parse --short $1`"
/linux/Documentation/translations/zh_TW/process/
H A Dsubmitting-patches.rst33 本文檔假設您正在使用 ``git`` 準備你的補丁。如果您不熟悉 ``git`` ，最好學習
42 如果您手頭沒有當前內核源代碼的存儲庫，請使用 ``git`` 獲取一份。您需要先獲取
45 git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
75 碼管理系統 ``git`` 中，那麼維護人員將非常感謝您。
116 如果補丁修復了特定提交中的錯誤，例如使用 ``git bisct`` 發現了一個問題，請使用
122 下列 ``git config`` 設置可以讓 ``git log``, ``git show`` 增加上述風格的顯示格式::
131 $ git log -1 --pretty=fixes 54a4f0239f2e
155 都能正常構建和運行。使用 ``git bisect`` 來追蹤問題的開發者可能會在任何地方分
235 是使用 ``git send-email`` 。https://git-send-email.io 有 ``git send-email``
238 如果你選擇不用 ``git send-email`` ：
[all …]
/linux/Documentation/translations/zh_CN/process/
H A Dsubmitting-patches.rst32 本文档假设您正在使用 ``git`` 准备你的补丁。如果您不熟悉 ``git`` ，最好学习
41 如果您手头没有当前内核源代码的存储库，请使用 ``git`` 获取一份。您需要先获取
44 git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
74 码管理系统 ``git`` 中，那么维护人员将非常感谢您。
115 如果补丁修复了特定提交中的错误，例如使用 ``git bisct`` 发现了一个问题，请使用
121 下列 ``git config`` 设置可以让 ``git log``, ``git show`` 增加上述风格的显示格式::
130 $ git log -1 --pretty=fixes 54a4f0239f2e
154 都能正常构建和运行。使用 ``git bisect`` 来追踪问题的开发者可能会在任何地方分
231 是使用 ``git send-email`` 。https://git-send-email.io 有 ``git send-email``
234 如果你选择不用 ``git send-email`` ：
[all …]
H A Dmaintainer-pgp-guide.rst33 - 分布式源仓库 (git)
36 git 仓库和 tarball 都带有创建官方内核版本的内核开发者的 PGP 签名。这
40 - git 仓库在所有标签上提供 PGP 签名
561 将 PGP 与 Git 结合使用
564 Git 的核心功能之一是它的分散性——一旦将仓库克隆到你的系统，你就拥有该
566 库的出现，人们如何验证他们的 linux.git 副本没有被恶意第三方篡改？
571 为了解决这两个问题，Git 引入了 PGP 集成。签名的标签通过确保其内容与创
575 .. _`自己与它无关`: https://github.com/jayphelps/git-blame-someone-else
577 配置 git 使用你的 PGP 密钥
581 它会成为你的默认密钥。但是，如果你碰巧有多个密钥，你可以告诉 git 应该
[all …]
/linux/Documentation/maintainer/
H A Dconfigure-git.rst1 Configuring Git
4 This chapter describes maintainer level git configuration.
9 ``-u <key-id>`` to ``git tag``. However, since you would *usually* use the same
13 git config user.signingkey "keyname"
15 Alternatively, edit your ``.git/config`` or ``~/.gitconfig`` file by hand::
22 You may need to tell ``git`` to use ``gpg2``::
46 This can be configured to happen automatically any time you issue ``git am``
47 by adding the following hook into your git::
49 $ git config am.messageid true
50 $ cat >.git/hooks/applypatch-msg <<'EOF'
[all …]
/linux/tools/verification/rv/
H A DREADME.txt22 $ git clone git://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git
27 $ git clone git://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git
/linux/tools/tracing/rtla/
H A DREADME.txt20 $ git clone git://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git
25 $ git clone git://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git
/linux/drivers/gpu/drm/ci/
H A Dcheck-patch.py16 repourl = "https://gitlab.freedesktop.org/%s.git" % os.environ["CI_MERGE_REQUEST_PROJECT_PATH"]
20 # ancestor between the user's branch and current git master.
22 subprocess.call(["git", "remote", "remove", "check-patch"], stdout=subprocess.DEVNULL, stderr=subpr…
23 subprocess.check_call(["git", "remote", "add", "check-patch", repourl])
24 subprocess.check_call(["git", "fetch", "check-patch", os.environ["CI_MERGE_REQUEST_TARGET_BRANCH_NA…
28 ancestor = subprocess.check_output(["git", "merge-base",
34 log = subprocess.check_output(["git", "log", "--format=%H %s",
38 subprocess.check_call(["git", "remote", "rm", "check-patch"])
51 "--git", ancestor + "..."])
/linux/scripts/dtc/
H A Dupdate-dtc-source.sh5 # This script assumes that the dtc and the linux git trees are in the
8 # in the kernel and creates a git commit updating them to the new
15 # relevant files into the kernel tree and create a git commit. The commit
43 git log --oneline scripts/dtc/ | grep 'upstream' | head -1 | sed -e 's/^.* \(.*\)/\1/'
52 dtc_version=$(git describe HEAD)
53 dtc_log=$(git log --oneline ${last_dtc_ver}..)
60 git add ${f}
64 git add libfdt/${f}
69 git add ./libfdt/libfdt.h
80 git commit -e -v -s -m "${commit_msg}"
/linux/tools/lib/perf/Documentation/
H A Dmanpage-base.xsl11 git.docbook.backslash and git.docbook.dot params
15 $git.docbook.backslash,'fB(',
17 $git.docbook.backslash,'fR')"/>
20 <xsl:value-of select="$git.docbook.dot"/>
27 $git.docbook.backslash,'fB',
29 '. ',$git.docbook.backslash,'fR')"/>
31 <xsl:value-of select="$git.docbook.dot"/>
/linux/Documentation/target/
H A Dtcm_mod_builder.rst32 …target:/mnt/sdb/lio-core-2.6.git/Documentation/target# python tcm_mod_builder.py -p iSCSI -m tcm_n…
33 tcm_dir: /mnt/sdb/lio-core-2.6.git/Documentation/target/../../
36 /mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000
39 /mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000
41 /mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000/tcm_nab5000_base.h
43 /mnt/sdb/lio-core-2.6.git/Documentation/target/../../include/target/target_core_fabric_ops.h
45 …/mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000/tcm_nab5000_fabric…
47 …/mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000/tcm_nab5000_fabric…
49 …/mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000/tcm_nab5000_config…
51 /mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000/Kbuild
[all …]
/linux/tools/testing/selftests/rcutorture/bin/
H A Dkvm-check-branches.sh14 # specification of commits is needed, please use "git rev-list" to
31 if ! git status > /dev/null 2>&1
33 echo '!!!' This script needs to run in a git archive. 1>&2
39 curcommit="`git status | head -1 | awk '{ print $NF }'`"
60 echo ' --- git branch ' $gitbr
63 for i in `git rev-list "$gitbr"`
74 git checkout $i > $resdir/$ds/$idir/git-checkout.out 2>&1
75 echo git checkout return code: $? "(Commit $ntry: $i)"
93 git checkout "$curcommit"

12345678910>>...16