[FFmpeg-cvslog] doc/faq: add @command{} in the tool debug entry.

Clément Bœsch git at videolan.org
Sun Sep 29 23:33:11 CEST 2013


ffmpeg | branch: master | Clément Bœsch <u at pkh.me> | Tue Sep 24 21:43:19 2013 +0200| [565fd3cc1a175854fbcf8d5db75a02b5df034299] | committer: Clément Bœsch

doc/faq: add @command{} in the tool debug entry.

> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=565fd3cc1a175854fbcf8d5db75a02b5df034299
---

 doc/faq.texi |    7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/doc/faq.texi b/doc/faq.texi
index 0bad57d..c47d9d9 100644
--- a/doc/faq.texi
+++ b/doc/faq.texi
@@ -475,9 +475,10 @@ read @uref{http://www.tux.org/lkml/#s15, "Programming Religion"}.
 
 @section Why are the ffmpeg programs devoid of debugging symbols?
 
-The build process creates ffmpeg_g, ffplay_g, etc. which contain full debug
-information. Those binaries are stripped to create ffmpeg, ffplay, etc. If
-you need the debug information, use the *_g versions.
+The build process creates @command{ffmpeg_g}, @command{ffplay_g}, etc. which
+contain full debug information. Those binaries are stripped to create
+ at command{ffmpeg}, @command{ffplay}, etc. If you need the debug information, use
+the *_g versions.
 
 @section I do not like the LGPL, can I contribute code under the GPL instead?
 



More information about the ffmpeg-cvslog mailing list