59 lines · plain
1Configuring Git2===============3 4This chapter describes maintainer level git configuration.5 6Tagged branches used in pull requests (see7Documentation/maintainer/pull-requests.rst) should be signed with the8developers public GPG key. Signed tags can be created by passing9``-u <key-id>`` to ``git tag``. However, since you would *usually* use the same10key for the project, you can set it in the configuration and use the ``-s``11flag. To set the default ``key-id`` use::12 13 git config user.signingkey "keyname"14 15Alternatively, edit your ``.git/config`` or ``~/.gitconfig`` file by hand::16 17 [user]18 name = Jane Developer19 email = jd@domain.org20 signingkey = jd@domain.org21 22You may need to tell ``git`` to use ``gpg2``::23 24 [gpg]25 program = /path/to/gpg226 27You may also like to tell ``gpg`` which ``tty`` to use (add to your shell28rc file)::29 30 export GPG_TTY=$(tty)31 32 33Creating commit links to lore.kernel.org34----------------------------------------35 36The web site https://lore.kernel.org is meant as a grand archive of all mail37list traffic concerning or influencing the kernel development. Storing archives38of patches here is a recommended practice, and when a maintainer applies a39patch to a subsystem tree, it is a good idea to provide a Link: tag with a40reference back to the lore archive so that people that browse the commit41history can find related discussions and rationale behind a certain change.42The link tag will look like this::43 44 Link: https://lore.kernel.org/r/<message-id>45 46This can be configured to happen automatically any time you issue ``git am``47by adding the following hook into your git::48 49 $ git config am.messageid true50 $ cat >.git/hooks/applypatch-msg <<'EOF'51 #!/bin/sh52 . git-sh-setup53 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 EOF58 $ chmod a+x .git/hooks/applypatch-msg59