Lines Matching refs:git

22 * The code is hosted in a public git repository.
39 The development process requires some familiarity with the ``git`` version control system.
40 Refer to the `Pro Git Book <http://www.git-scm.com/book/>`_ for further information.
78     T: git://dpdk.org/next/dpdk-next-crypto
133     git clone git://dpdk.org/dpdk
134     git clone https://dpdk.org/git/dpdk
136 sub-repositories (`list <https://git.dpdk.org/next>`_)::
138     git clone git://dpdk.org/next/dpdk-next-*
139     git clone https://dpdk.org/git/next/dpdk-next-*
170 …Each commit should compile on its own to allow for ``git bisect`` and continuous integration testi…
190 As a guide to how patches should be structured run ``git log`` on similar files.
196 The first, summary, line of the git commit message becomes the subject line of the patch email.
205 * It should be prefixed with the component name (use git log to check existing components).
218 The is generally added by ``git send-email`` or ``git format-patch``, see below.
237       git commit --signoff # or -s
256   You can generate the required lines using the following git alias, which prints
259      git config alias.fixline "log -1 --abbrev=12 --format='Fixes: %h (\"%s\")%nCc: %ae'"
261   The output of ``git fixline <SHA>`` must then be added to the commit message::
362 It is possible to send patches directly from git but for new contributors it is recommended to gene…
363 patches with ``git format-patch`` and then when everything looks okay, and the patches have been ch…
364 send them with ``git send-email``.
366 Here are some examples of using ``git format-patch`` to generate patches:
371    git format-patch -1
374    git format-patch -3
377    git format-patch -3 -o ~/patch/
380    git format-patch -3 -o ~/patch/ --cover-letter
383    git format-patch -3 -o ~/patch/ -v 2
453 Then the git logs should be checked using the ``check-git-log.sh`` script.
457    check-git-log.sh [-h] [-nX|-r range]
460 and the -r option allows the user specify a ``git log`` range.
488 git tag of the most recent release of DPDK in ``DPDK_ABI_REF_VERSION``.
504 Patches should be sent to the mailing list using ``git send-email``.
513 See the `Git send-email <https://git-scm.com/docs/git-send-email>`_ documentation for more details.
519    git send-email --to [email protected] --cc [email protected] 000*.patch
523   git send-email --to-cmd ./devtools/get-maintainer.sh --cc [email protected] 000*.patch
527    git send-email --to [email protected] 000*.patch
533    git send-email --to [email protected] --in-reply-to <[email protected]> 000*.patch
541 Experienced committers may send patches directly with ``git send-email`` without the ``git format-p…
555 using ``git send-email --subject-prefix='PATCH 16.11' ...``
622       git format-patch -3 -v 2
647 …two weeks. After that time, the patch should be merged into the relevant git tree for the next rel…