From 07f77dad7afb5254d3d45158a2623f64b9290c8f Mon Sep 17 00:00:00 2001
From: Diego Biurrun <diego@biurrun.de>
Date: Thu, 1 Oct 2009 11:58:34 +0000
Subject: [PATCH] Explain the process of patch review and commit a bit.

Originally committed as revision 20119 to svn://svn.ffmpeg.org/ffmpeg/trunk
---
 doc/developer.texi | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/doc/developer.texi b/doc/developer.texi
index aec3c660081..f84885d3af7 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -267,6 +267,16 @@ and has no lrint()')
 Also please if you send several patches, send each patch as a separate mail,
 do not attach several unrelated patches to the same mail.
 
+Your patch will be reviewed on the mailing list. You will likely be asked
+to make some changes and are expected to send in an improved version that
+incorporates the requests from the review. This process may go through
+several iterations. Once your patch is deemed good enough, some developer
+will pick it up and commit it to the official FFmpeg tree.
+
+Give us a few days to react. But if some time passes without reaction,
+send a reminder by email. Your patch should eventually be dealt with.
+
+
 @section New codecs or formats checklist
 
 @enumerate
-- 
GitLab