History

doc/developer: add description about safely sending patches via E-Mail clients

Soft Works committed 5 years ago

Commit 89ba6e91 parent fba4d6f1 file · +16 −0Browse files

Unified · Split

doc/developer.texi+16−0
@@ -494,6 +494,22 @@ patch is inline or attached per mail. · 493 unmodified lines
494You can check @url{https://patchwork.ffmpeg.org}, if your patch does not show up, its mime type494You can check @url{https://patchwork.ffmpeg.org}, if your patch does not show up, its mime type
495likely was wrong.495likely was wrong.
496 496
497@subheading Sending patches from email clients
498Using @code{git send-email} might not be desirable for everyone. The
499following trick allows to send patches via email clients in a safe
500way. It has been tested with Outlook and Thunderbird (with X-Unsent
501extension) and might work with other applications.
502
503Create your patch like this:
504
505@verbatim
506git format-patch -s -o "outputfolder" --add-header "X-Unsent: 1" --suffix .eml --to ffmpeg-devel@ffmpeg.org -1 1a2b3c4d
507@end verbatim
508
509Now you'll just need to open the eml file with the email application
510and execute 'Send'.
511
512@subheading Reviews
497Your patch will be reviewed on the mailing list. You will likely be asked513Your patch will be reviewed on the mailing list. You will likely be asked
498to make some changes and are expected to send in an improved version that514to make some changes and are expected to send in an improved version that
499incorporates the requests from the review. This process may go through515incorporates the requests from the review. This process may go through

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t