diff options
| author | Michael Niedermayer <michael@niedermayer.cc> | 2024-06-12 19:37:15 +0200 |
|---|---|---|
| committer | Michael Niedermayer <michael@niedermayer.cc> | 2024-06-13 00:39:57 +0200 |
| commit | 959cb2e2e36cad50b88d45c1201c2c3d64d4e48c (patch) | |
| tree | dbaf9d9e1fa61dfb1d219f85ef43ec0656e1b60c /doc | |
| parent | 9fb6f024c3db2c19aca7f5f93c6843b7e5d1eecf (diff) | |
| download | ffmpeg-959cb2e2e36cad50b88d45c1201c2c3d64d4e48c.tar.gz | |
doc/developer: Provide information about git send-email and gmail
The 2 links are the clearest i found.
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/developer.texi | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/developer.texi b/doc/developer.texi index 89e8bec60f..41b21938ef 100644 --- a/doc/developer.texi +++ b/doc/developer.texi @@ -638,6 +638,11 @@ patch is inline or attached per mail. You can check @url{https://patchwork.ffmpeg.org}, if your patch does not show up, its mime type likely was wrong. +@subheading How to setup git send-email? + +Please see @url{https://git-send-email.io/}. +For gmail additionally see @url{https://shallowsky.com/blog/tech/email/gmail-app-passwds.html}. + @subheading Sending patches from email clients Using @code{git send-email} might not be desirable for everyone. The following trick allows to send patches via email clients in a safe |