~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/maintainer/configure-git.rst

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

  1 Configuring Git
  2 ===============
  3 
  4 This chapter describes maintainer level git configuration.
  5 
  6 Tagged branches used in pull requests (see
  7 Documentation/maintainer/pull-requests.rst) should be signed with the
  8 developers public GPG key. Signed tags can be created by passing
  9 ``-u <key-id>`` to ``git tag``. However, since you would *usually* use the same
 10 key for the project, you can set it in the configuration and use the ``-s``
 11 flag. To set the default ``key-id`` use::
 12 
 13         git config user.signingkey "keyname"
 14 
 15 Alternatively, edit your ``.git/config`` or ``~/.gitconfig`` file by hand::
 16 
 17         [user]
 18                 name = Jane Developer
 19                 email = jd@domain.org
 20                 signingkey = jd@domain.org
 21 
 22 You may need to tell ``git`` to use ``gpg2``::
 23 
 24         [gpg]
 25                 program = /path/to/gpg2
 26 
 27 You may also like to tell ``gpg`` which ``tty`` to use (add to your shell
 28 rc file)::
 29 
 30         export GPG_TTY=$(tty)
 31 
 32 
 33 Creating commit links to lore.kernel.org
 34 ----------------------------------------
 35 
 36 The web site https://lore.kernel.org is meant as a grand archive of all mail
 37 list traffic concerning or influencing the kernel development. Storing archives
 38 of patches here is a recommended practice, and when a maintainer applies a
 39 patch to a subsystem tree, it is a good idea to provide a Link: tag with a
 40 reference back to the lore archive so that people that browse the commit
 41 history can find related discussions and rationale behind a certain change.
 42 The link tag will look like this::
 43 
 44     Link: https://lore.kernel.org/r/<message-id>
 45 
 46 This can be configured to happen automatically any time you issue ``git am``
 47 by adding the following hook into your git::
 48 
 49         $ git config am.messageid true
 50         $ cat >.git/hooks/applypatch-msg <<'EOF'
 51         #!/bin/sh
 52         . git-sh-setup
 53         perl -pi -e 's|^Message-I[dD]:\s*<?([^>]+)>?$|Link: https://lore.kernel.org/r/$1|g;' "$1"
 54         test -x "$GIT_DIR/hooks/commit-msg" &&
 55                 exec "$GIT_DIR/hooks/commit-msg" ${1+"$@"}
 56         :
 57         EOF
 58         $ chmod a+x .git/hooks/applypatch-msg

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php