aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorcompn <compn@ffmpeg.org>2024-11-08 15:59:13 +1000
committercompn <compn@ffmpeg.org>2024-11-08 15:59:13 +1000
commitf4ba5b083c95b618603394a210c113a24968d68f (patch)
treeb1884022282549b720b894fcf824523d19bc77f9
parent11c703be3176174c2ddb0f3893d10f3ed1accb89 (diff)
downloadffmpeg-f4ba5b083c95b618603394a210c113a24968d68f.tar.gz
doc/git-howto: remove outdated line about gitolite
-rw-r--r--doc/git-howto.texi1
1 files changed, 0 insertions, 1 deletions
diff --git a/doc/git-howto.texi b/doc/git-howto.texi
index 075b188abe..0a8d8de1d7 100644
--- a/doc/git-howto.texi
+++ b/doc/git-howto.texi
@@ -71,7 +71,6 @@ git clone git@@ffmpeg.org:ffmpeg-web <target>
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: