mirror of
https://github.com/torvalds/linux.git
synced 2026-01-12 00:42:35 +08:00
944df7a314
As stated definitively by Linus, the use of Link: tags should be limited to situations where there is additional useful information to be found at the far end of the link. Update our documentation to reflect that policy, and to remove the suggestion for a Git hook to add those tags automatically. Link: https://lore.kernel.org/all/CAHk-=wh5AyuvEhNY9a57v-vwyr7EkPVRUKMPwj92yF_K0dJHVg@mail.gmail.com/ Cc: Linus Walleij <linus.walleij@linaro.org> Reviewed-by: Randy Dunlap <rdunlap@infradead.org> Reviewed-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Message-ID: <87segwyc3p.fsf@trenco.lwn.net>
31 lines
863 B
ReStructuredText
31 lines
863 B
ReStructuredText
Configuring Git
|
|
===============
|
|
|
|
This chapter describes maintainer level git configuration.
|
|
|
|
Tagged branches used in pull requests (see
|
|
Documentation/maintainer/pull-requests.rst) should be signed with the
|
|
developers public GPG key. Signed tags can be created by passing
|
|
``-u <key-id>`` to ``git tag``. However, since you would *usually* use the same
|
|
key for the project, you can set it in the configuration and use the ``-s``
|
|
flag. To set the default ``key-id`` use::
|
|
|
|
git config user.signingkey "keyname"
|
|
|
|
Alternatively, edit your ``.git/config`` or ``~/.gitconfig`` file by hand::
|
|
|
|
[user]
|
|
name = Jane Developer
|
|
email = jd@domain.org
|
|
signingkey = jd@domain.org
|
|
|
|
You may need to tell ``git`` to use ``gpg2``::
|
|
|
|
[gpg]
|
|
program = /path/to/gpg2
|
|
|
|
You may also like to tell ``gpg`` which ``tty`` to use (add to your shell
|
|
rc file)::
|
|
|
|
export GPG_TTY=$(tty)
|