Searched full:git (Results 1 – 25 of 909) sorted by relevance
12345678910>>...37
| /kernel/linux/linux-5.10/ |
| D | MAINTAINERS | 44 script will be best if you have git installed and are making
45 your changes in a branch derived from Linus' latest git tree.
108 Type is one of: git, hg, quilt, stgit, topgit
127 get_maintainer will not look at git log history when an F: pattern
128 match occurs. When an N: match occurs, git log history is used
129 to also notify the people that have git commit signatures.
193 T: git git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git
194 T: git git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git
216 T: git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
233 T: git git://git.kernel.org/pub/scm/linux/kernel/git/ericvh/v9fs.git
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | bug-bisect.rst | 29 Using the provided tools with ``git`` makes finding bugs easy provided the bug
34 - build the Kernel from its git source
37 $ git bisect start
41 $ git bisect bad [commit]
45 $ git bisect good [commit]
48 - interact with git bisect by using either::
50 $ git bisect good
54 $ git bisect bad
57 - After some interactions, git bisect will give you the changeset that
63 $ git bisect start
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | bug-bisect.rst | 29 Using the provided tools with ``git`` makes finding bugs easy provided the bug
34 - build the Kernel from its git source
37 $ git bisect start
41 $ git bisect bad [commit]
45 $ git bisect good [commit]
48 - interact with git bisect by using either::
50 $ git bisect good
54 $ git bisect bad
57 - After some interactions, git bisect will give you the changeset that
63 $ git bisect start
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/Documentation/ |
| D | examples.txt | 66 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 …]
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | examples.txt | 66 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 …]
|
| /kernel/linux/linux-6.6/Documentation/translations/zh_CN/admin-guide/ |
| D | bug-bisect.rst | 34 使用 ``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 …]
|
| /kernel/linux/linux-6.6/ |
| D | MAINTAINERS | 32 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
141 T: git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
159 T: git git://git.kernel.org/pub/scm/linux/kernel/git/ericvh/v9fs.git
160 T: git git://github.com/martinetd/linux.git
180 T: git git://linuxtv.org/anttip/media_tree.git
[all …]
|
| /kernel/linux/linux-6.6/Documentation/translations/zh_TW/admin-guide/ |
| D | bug-bisect.rst | 37 使用 ``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 …]
|
| /kernel/linux/linux-5.10/scripts/ |
| D | setlocalversion | 5 # control systems git, mercurial (hg) and subversion (svn).
46 # Check for git and a git repo.
47 if test -z "$(git rev-parse --show-cdup 2>/dev/null)" &&
48 head=$(git rev-parse --verify HEAD 2>/dev/null); then
52 if [ -z "$(git describe --exact-match 2>/dev/null)" ]; then
55 # running further git commands
65 # independent of git version, local
71 if atag="$(git describe --abbrev=12 2>/dev/null)"; then
82 # Is this git on svn?
83 if git config --get svn-remote.svn.url >/dev/null; then
[all …]
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | 7.AdvancedTopics.rst | 11 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 …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | 7.AdvancedTopics.rst | 11 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 …]
|
| /kernel/linux/linux-6.6/Documentation/translations/it_IT/process/ |
| D | 7.AdvancedTopics.rst | 16 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 …]
|
| /kernel/linux/linux-5.10/Documentation/translations/it_IT/process/ |
| D | 7.AdvancedTopics.rst | 16 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 http://git-scm.com/
40 http://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 …]
|
| /kernel/linux/linux-6.6/Documentation/translations/zh_CN/maintainer/ |
| D | pull-requests.rst | 41 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
|
| D | configure-git.rst | 3 :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
|
| /kernel/linux/linux-6.6/scripts/ |
| D | setlocalversion | 5 # control system git.
37 [ "$(git cat-file -t "$tag" 2> /dev/null)" = tag ] || return 1
41 set -- $(git rev-list --count --left-right "$tag"...HEAD 2> /dev/null)
44 # string comparison, because $1 is empty if the 'git rev-list'
73 if test -n "$(git rev-parse --show-cdup 2>/dev/null)"; then
77 if ! head=$(git rev-parse --verify HEAD 2>/dev/null); then
114 # running further git commands
137 # You cannot use 'git describe --dirty' because it tries to create
138 # .git/index.lock .
139 # First, with git-status, but --no-optional-locks is only supported in
[all …]
|
| /kernel/linux/linux-6.6/Documentation/translations/zh_CN/process/ |
| D | submitting-patches.rst | 32 本文档假设您正在使用 ``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`` 来追踪问题的开发者可能会在任何地方分
234 是使用 ``git send-email`` 。https://git-send-email.io 有 ``git send-email``
237 如果你选择不用 ``git send-email`` ：
[all …]
|
| /kernel/linux/linux-5.10/Documentation/maintainer/ |
| D | configure-git.rst | 3 Configure Git
6 This chapter describes maintainer level git configuration.
10 tags can be created by passing the ``-u`` flag to ``git tag``. However,
15 git config user.signingkey "keyname"
17 Alternatively, edit your ``.git/config`` or ``~/.gitconfig`` file by hand:
25 You may need to tell ``git`` to use ``gpg2``
50 This can be configured to happen automatically any time you issue ``git am``
51 by adding the following hook into your git:
55 $ git config am.messageid true
56 $ cat >.git/hooks/applypatch-msg <<'EOF'
[all …]
|
| D | pull-requests.rst | 40 git tag -s char-misc-4.15-rc1 char-misc-next
44 (see :ref:`Documentation/maintainer/configure-git.rst <configuregit>`).
49 When you run the above command ``git`` will drop you into an editor and ask
123 The tag message format is just like a git commit id. One line at the top
129 git push origin char-misc-4.15-rc1
135 The last thing to do is create the pull request message. ``git`` handily
136 will do this for you with the ``git request-pull`` command, but it needs a
141 …git request-pull master git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ char-m…
145 This is asking git to compare the difference from the
149 git:// protocol to pull from. If you wish to use https://, that
[all …]
|
| /kernel/linux/linux-6.6/Documentation/maintainer/ |
| D | configure-git.rst | 1 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 …]
|
| D | pull-requests.rst | 38 git tag -s char-misc-4.15-rc1 char-misc-next
42 (see Documentation/maintainer/configure-git.rst).
47 When you run the above command ``git`` will drop you into an editor and ask
121 The tag message format is just like a git commit id. One line at the top
127 git push origin char-misc-4.15-rc1
133 The last thing to do is create the pull request message. ``git`` handily
134 will do this for you with the ``git request-pull`` command, but it needs a
139 …git request-pull master git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ char-m…
143 This is asking git to compare the difference from the
147 git:// protocol to pull from. If you wish to use https://, that
[all …]
|
| /kernel/linux/linux-6.6/tools/tracing/rtla/ |
| D | README.txt | 19 $ git clone git://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git
24 $ git clone git://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git
|
| /kernel/linux/linux-6.6/tools/verification/rv/ |
| D | README.txt | 22 $ 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
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/ci/ |
| D | check-patch.py | 16 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 + "..."])
|
| /kernel/linux/linux-6.6/Documentation/translations/zh_TW/process/ |
| D | submitting-patches.rst | 42 git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
94 如果你用 ``git`` , ``git rebase -i`` 可以幫助你這一點。如果你不用 ``git``,
154 如果修補程序修復了特定提交中的錯誤，例如，使用 ``git bisct`` ，請使用帶有前
160 下列 ``git config`` 設置可以添加讓 ``git log``, ``git show`` 漂亮的顯示格式::
185 都能正常構建和運行。使用 ``git bisect`` 來追蹤問題的開發者可能會在任何時
492 本節描述如何格式化補丁本身。請注意，如果您的補丁存儲在 ``Git`` 存儲庫中，則
493 可以使用 ``git format-patch`` 進行正確的補丁格式設置。但是，這些工具無法創建
525 記住 e-mail 的「一句話概述」會成爲該補丁的全局唯一標識。它會蔓延到 git
528 章。當人們在兩三個月後使用諸如 ``gitk`` 或 ``git log --oneline`` 之類
575 手動添加回復補丁的的標題頭(In-Reply_To:) 是有幫助的（例如，使用 ``git send-email`` ）
[all …]
|
12345678910>>...37