Message ID | 20240613133520.950637-1-michael@niedermayer.cc |
---|---|
State | New |
Headers | show |
Series | [FFmpeg-devel] doc/developer: point to git examples for gmail instead | expand |
Context | Check | Description |
---|---|---|
yinshiyou/make_loongarch64 | success | Make finished |
yinshiyou/make_fate_loongarch64 | success | Make fate finished |
andriy/make_x86 | success | Make finished |
andriy/make_fate_x86 | success | Make fate finished |
diff --git a/doc/developer.texi b/doc/developer.texi index 41b21938ef8..f3ad4e08fa7 100644 --- a/doc/developer.texi +++ b/doc/developer.texi @@ -641,7 +641,7 @@ 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}. +For gmail additionally see @url{https://git-scm.com/docs/git-send-email#_examples}. @subheading Sending patches from email clients Using @code{git send-email} might not be desirable for everyone. The
This was suggested by kasper93 on IRC Do people prefer this or the previous ? should we have both links instead ? Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> --- doc/developer.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)