ffmpeg | branch: master | Andreas Cadhalpun <andreas.cadhal...@googlemail.com> | Wed Nov 25 00:52:39 2015 +0100| [fb1bf4454e6e8d70c001969c0e423399235d3224] | committer: Andreas Cadhalpun
git-howto: mention how to clone ffmpeg-web Signed-off-by: Andreas Cadhalpun <andreas.cadhal...@googlemail.com> > http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=fb1bf4454e6e8d70c001969c0e423399235d3224 --- doc/git-howto.texi | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/doc/git-howto.texi b/doc/git-howto.texi index bf37bcc..e5e3c81 100644 --- a/doc/git-howto.texi +++ b/doc/git-howto.texi @@ -65,6 +65,21 @@ git clone git@@source.ffmpeg.org:ffmpeg <target> This will put the FFmpeg sources into the directory @var{<target>} and let you push back your changes to the remote repository. +@example +git clone gil@@ffmpeg.org:ffmpeg-web <target> +@end example + +This will put the source of the FFmpeg website into the directory +@var{<target>} and let you push back your changes to the remote repository. +(Note that @var{gil} stands for GItoLite and is not a typo of @var{git}.) + +If you don't have write-access to the ffmpeg-web repository, you can +create patches after making a read-only ffmpeg-web clone: + +@example +git clone git://ffmpeg.org/ffmpeg-web <target> +@end example + Make sure that you do not have Windows line endings in your checkouts, otherwise you may experience spurious compilation failures. One way to achieve this is to run _______________________________________________ ffmpeg-cvslog mailing list ffmpeg-cvslog@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-cvslog
