[Ffmpeg-devel] another policy change[RFC][PATCH]
Sun Jul 9 05:09:13 CEST 2006
is the attached change, maybe with more clear wording ok?
the intention is that a developer should make it clear before that he
intends to commit a change if there are no replies to his patch ...
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
In the past you could go to a library and read, borrow or copy any book
Today you'd get arrested for mere telling someone where the library is
-------------- next part --------------
--- ffmpeg-doc.texi (revision 5676)
+++ ffmpeg-doc.texi (working copy)
@@ -1275,6 +1275,8 @@
Send a patch to ffmpeg-devel instead. If noone answers within a reasonable
timeframe (12h for build failures and security fixes, 3 days small changes,
1 week for big patches) then commit your patch if you think it's OK.
+ You should also make it clear in your post to ffmpeg-dev when you will
+ commit your changes in case of lack of comments.
Also note, the maintainer can simply ask for more time to review!
Subscribe to the ffmpeg-cvslog mailing list. The diffs of all commits
More information about the ffmpeg-devel