星火直播PC
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

git-howto.html 20KB

3 lat temu
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519
  1. <!DOCTYPE html>
  2. <html lang="en">
  3. <head>
  4. <meta charset="utf-8" />
  5. <meta http-equiv="X-UA-Compatible" content="IE=edge" />
  6. <title>FFmpeg documentation</title>
  7. <link rel="stylesheet" href="bootstrap.min.css" />
  8. <link rel="stylesheet" href="style.min.css" />
  9. <meta name="description" content="Using Git to develop FFmpeg: ">
  10. <meta name="keywords" content="FFmpeg documentation : Using Git to develop FFmpeg: ">
  11. <meta name="Generator" content="texi2html 5.0">
  12. <!-- Created on March 9, 2020 by texi2html 5.0 -->
  13. <!--
  14. texi2html was written by:
  15. Lionel Cons <Lionel.Cons@cern.ch> (original author)
  16. Karl Berry <karl@freefriends.org>
  17. Olaf Bachmann <obachman@mathematik.uni-kl.de>
  18. and many others.
  19. Maintained by: Many creative people.
  20. Send bugs and suggestions to <texi2html-bug@nongnu.org>
  21. -->
  22. <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  23. </head>
  24. <body>
  25. <div class="container">
  26. <h1 class="titlefont">Using Git to develop FFmpeg</h1>
  27. <hr>
  28. <a name="SEC_Top"></a>
  29. <a name="SEC_Contents"></a>
  30. <h1>Table of Contents</h1>
  31. <div class="contents">
  32. <ul class="no-bullet">
  33. <li><a name="toc-Introduction" href="#Introduction">1 Introduction</a></li>
  34. <li><a name="toc-Basics-Usage" href="#Basics-Usage">2 Basics Usage</a>
  35. <ul class="no-bullet">
  36. <li><a name="toc-Get-Git" href="#Get-Git">2.1 Get Git</a></li>
  37. <li><a name="toc-Cloning-the-source-tree" href="#Cloning-the-source-tree">2.2 Cloning the source tree</a></li>
  38. <li><a name="toc-Updating-the-source-tree-to-the-latest-revision-1" href="#Updating-the-source-tree-to-the-latest-revision-1">2.3 Updating the source tree to the latest revision</a></li>
  39. <li><a name="toc-Rebasing-your-local-branches" href="#Rebasing-your-local-branches">2.4 Rebasing your local branches</a></li>
  40. <li><a name="toc-Adding_002fremoving-files_002fdirectories" href="#Adding_002fremoving-files_002fdirectories">2.5 Adding/removing files/directories</a></li>
  41. <li><a name="toc-Showing-modifications" href="#Showing-modifications">2.6 Showing modifications</a></li>
  42. <li><a name="toc-Inspecting-the-changelog" href="#Inspecting-the-changelog">2.7 Inspecting the changelog</a></li>
  43. <li><a name="toc-Checking-source-tree-status" href="#Checking-source-tree-status">2.8 Checking source tree status</a></li>
  44. <li><a name="toc-Committing" href="#Committing">2.9 Committing</a></li>
  45. <li><a name="toc-Preparing-a-patchset" href="#Preparing-a-patchset">2.10 Preparing a patchset</a></li>
  46. <li><a name="toc-Sending-patches-for-review" href="#Sending-patches-for-review">2.11 Sending patches for review</a></li>
  47. <li><a name="toc-Renaming_002fmoving_002fcopying-files-or-contents-of-files" href="#Renaming_002fmoving_002fcopying-files-or-contents-of-files">2.12 Renaming/moving/copying files or contents of files</a></li>
  48. </ul></li>
  49. <li><a name="toc-Git-configuration" href="#Git-configuration">3 Git configuration</a>
  50. <ul class="no-bullet">
  51. <li><a name="toc-Personal-Git-installation" href="#Personal-Git-installation">3.1 Personal Git installation</a></li>
  52. <li><a name="toc-Repository-configuration" href="#Repository-configuration">3.2 Repository configuration</a></li>
  53. </ul></li>
  54. <li><a name="toc-FFmpeg-specific" href="#FFmpeg-specific">4 FFmpeg specific</a>
  55. <ul class="no-bullet">
  56. <li><a name="toc-Reverting-broken-commits" href="#Reverting-broken-commits">4.1 Reverting broken commits</a></li>
  57. <li><a name="toc-Pushing-changes-to-remote-trees" href="#Pushing-changes-to-remote-trees">4.2 Pushing changes to remote trees</a></li>
  58. <li><a name="toc-Finding-a-specific-svn-revision" href="#Finding-a-specific-svn-revision">4.3 Finding a specific svn revision</a></li>
  59. </ul></li>
  60. <li><a name="toc-Pre_002dpush-checklist" href="#Pre_002dpush-checklist">5 Pre-push checklist</a></li>
  61. <li><a name="toc-Server-Issues" href="#Server-Issues">6 Server Issues</a></li>
  62. </ul>
  63. </div>
  64. <hr size="6">
  65. <a name="Introduction"></a>
  66. <h1 class="chapter"><a href="git-howto.html#toc-Introduction">1 Introduction</a></h1>
  67. <p>This document aims in giving some quick references on a set of useful Git
  68. commands. You should always use the extensive and detailed documentation
  69. provided directly by Git:
  70. </p>
  71. <div class="example">
  72. <pre class="example">git --help
  73. man git
  74. </pre></div>
  75. <p>shows you the available subcommands,
  76. </p>
  77. <div class="example">
  78. <pre class="example">git &lt;command&gt; --help
  79. man git-&lt;command&gt;
  80. </pre></div>
  81. <p>shows information about the subcommand &lt;command&gt;.
  82. </p>
  83. <p>Additional information could be found on the
  84. <a href="http://gitref.org">Git Reference</a> website.
  85. </p>
  86. <p>For more information about the Git project, visit the
  87. <a href="http://git-scm.com/">Git website</a>.
  88. </p>
  89. <p>Consult these resources whenever you have problems, they are quite exhaustive.
  90. </p>
  91. <p>What follows now is a basic introduction to Git and some FFmpeg-specific
  92. guidelines to ease the contribution to the project.
  93. </p>
  94. <a name="Basics-Usage"></a>
  95. <h1 class="chapter"><a href="git-howto.html#toc-Basics-Usage">2 Basics Usage</a></h1>
  96. <a name="Get-Git"></a>
  97. <h2 class="section"><a href="git-howto.html#toc-Get-Git">2.1 Get Git</a></h2>
  98. <p>You can get Git from <a href="http://git-scm.com/">http://git-scm.com/</a>
  99. Most distribution and operating system provide a package for it.
  100. </p>
  101. <a name="Cloning-the-source-tree"></a>
  102. <h2 class="section"><a href="git-howto.html#toc-Cloning-the-source-tree">2.2 Cloning the source tree</a></h2>
  103. <div class="example">
  104. <pre class="example">git clone git://source.ffmpeg.org/ffmpeg &lt;target&gt;
  105. </pre></div>
  106. <p>This will put the FFmpeg sources into the directory <var>&lt;target&gt;</var>.
  107. </p>
  108. <div class="example">
  109. <pre class="example">git clone git@source.ffmpeg.org:ffmpeg &lt;target&gt;
  110. </pre></div>
  111. <p>This will put the FFmpeg sources into the directory <var>&lt;target&gt;</var> and let
  112. you push back your changes to the remote repository.
  113. </p>
  114. <div class="example">
  115. <pre class="example">git clone gil@ffmpeg.org:ffmpeg-web &lt;target&gt;
  116. </pre></div>
  117. <p>This will put the source of the FFmpeg website into the directory
  118. <var>&lt;target&gt;</var> and let you push back your changes to the remote repository.
  119. (Note that <var>gil</var> stands for GItoLite and is not a typo of <var>git</var>.)
  120. </p>
  121. <p>If you don&rsquo;t have write-access to the ffmpeg-web repository, you can
  122. create patches after making a read-only ffmpeg-web clone:
  123. </p>
  124. <div class="example">
  125. <pre class="example">git clone git://ffmpeg.org/ffmpeg-web &lt;target&gt;
  126. </pre></div>
  127. <p>Make sure that you do not have Windows line endings in your checkouts,
  128. otherwise you may experience spurious compilation failures. One way to
  129. achieve this is to run
  130. </p>
  131. <div class="example">
  132. <pre class="example">git config --global core.autocrlf false
  133. </pre></div>
  134. <p><a name="Updating-the-source-tree-to-the-latest-revision"></a>
  135. </p><a name="Updating-the-source-tree-to-the-latest-revision-1"></a>
  136. <h2 class="section"><a href="git-howto.html#toc-Updating-the-source-tree-to-the-latest-revision-1">2.3 Updating the source tree to the latest revision</a></h2>
  137. <div class="example">
  138. <pre class="example">git pull (--rebase)
  139. </pre></div>
  140. <p>pulls in the latest changes from the tracked branch. The tracked branch
  141. can be remote. By default the master branch tracks the branch master in
  142. the remote origin.
  143. </p>
  144. <div class="float alert alert-warning">
  145. <p><code>--rebase</code> (see below) is recommended.
  146. </p></div>
  147. <a name="Rebasing-your-local-branches"></a>
  148. <h2 class="section"><a href="git-howto.html#toc-Rebasing-your-local-branches">2.4 Rebasing your local branches</a></h2>
  149. <div class="example">
  150. <pre class="example">git pull --rebase
  151. </pre></div>
  152. <p>fetches the changes from the main repository and replays your local commits
  153. over it. This is required to keep all your local changes at the top of
  154. FFmpeg&rsquo;s master tree. The master tree will reject pushes with merge commits.
  155. </p>
  156. <a name="Adding_002fremoving-files_002fdirectories"></a>
  157. <h2 class="section"><a href="git-howto.html#toc-Adding_002fremoving-files_002fdirectories">2.5 Adding/removing files/directories</a></h2>
  158. <div class="example">
  159. <pre class="example">git add [-A] &lt;filename/dirname&gt;
  160. git rm [-r] &lt;filename/dirname&gt;
  161. </pre></div>
  162. <p>Git needs to get notified of all changes you make to your working
  163. directory that makes files appear or disappear.
  164. Line moves across files are automatically tracked.
  165. </p>
  166. <a name="Showing-modifications"></a>
  167. <h2 class="section"><a href="git-howto.html#toc-Showing-modifications">2.6 Showing modifications</a></h2>
  168. <div class="example">
  169. <pre class="example">git diff &lt;filename(s)&gt;
  170. </pre></div>
  171. <p>will show all local modifications in your working directory as unified diff.
  172. </p>
  173. <a name="Inspecting-the-changelog"></a>
  174. <h2 class="section"><a href="git-howto.html#toc-Inspecting-the-changelog">2.7 Inspecting the changelog</a></h2>
  175. <div class="example">
  176. <pre class="example">git log &lt;filename(s)&gt;
  177. </pre></div>
  178. <p>You may also use the graphical tools like <code>gitview</code> or <code>gitk</code>
  179. or the web interface available at <a href="http://source.ffmpeg.org/">http://source.ffmpeg.org/</a>.
  180. </p>
  181. <a name="Checking-source-tree-status"></a>
  182. <h2 class="section"><a href="git-howto.html#toc-Checking-source-tree-status">2.8 Checking source tree status</a></h2>
  183. <div class="example">
  184. <pre class="example">git status
  185. </pre></div>
  186. <p>detects all the changes you made and lists what actions will be taken in case
  187. of a commit (additions, modifications, deletions, etc.).
  188. </p>
  189. <a name="Committing"></a>
  190. <h2 class="section"><a href="git-howto.html#toc-Committing">2.9 Committing</a></h2>
  191. <div class="example">
  192. <pre class="example">git diff --check
  193. </pre></div>
  194. <p>to double check your changes before committing them to avoid trouble later
  195. on. All experienced developers do this on each and every commit, no matter
  196. how small.
  197. </p>
  198. <p>Every one of them has been saved from looking like a fool by this many times.
  199. It&rsquo;s very easy for stray debug output or cosmetic modifications to slip in,
  200. please avoid problems through this extra level of scrutiny.
  201. </p>
  202. <p>For cosmetics-only commits you should get (almost) empty output from
  203. </p>
  204. <div class="example">
  205. <pre class="example">git diff -w -b &lt;filename(s)&gt;
  206. </pre></div>
  207. <p>Also check the output of
  208. </p>
  209. <div class="example">
  210. <pre class="example">git status
  211. </pre></div>
  212. <p>to make sure you don&rsquo;t have untracked files or deletions.
  213. </p>
  214. <div class="example">
  215. <pre class="example">git add [-i|-p|-A] &lt;filenames/dirnames&gt;
  216. </pre></div>
  217. <p>Make sure you have told Git your name and email address
  218. </p>
  219. <div class="example">
  220. <pre class="example">git config --global user.name &quot;My Name&quot;
  221. git config --global user.email my@email.invalid
  222. </pre></div>
  223. <p>Use &lsquo;<samp>--global</samp>&rsquo; to set the global configuration for all your Git checkouts.
  224. </p>
  225. <p>Git will select the changes to the files for commit. Optionally you can use
  226. the interactive or the patch mode to select hunk by hunk what should be
  227. added to the commit.
  228. </p>
  229. <div class="example">
  230. <pre class="example">git commit
  231. </pre></div>
  232. <p>Git will commit the selected changes to your current local branch.
  233. </p>
  234. <p>You will be prompted for a log message in an editor, which is either
  235. set in your personal configuration file through
  236. </p>
  237. <div class="example">
  238. <pre class="example">git config --global core.editor
  239. </pre></div>
  240. <p>or set by one of the following environment variables:
  241. <var>GIT_EDITOR</var>, <var>VISUAL</var> or <var>EDITOR</var>.
  242. </p>
  243. <p>Log messages should be concise but descriptive. Explain why you made a change,
  244. what you did will be obvious from the changes themselves most of the time.
  245. Saying just &quot;bug fix&quot; or &quot;10l&quot; is bad. Remember that people of varying skill
  246. levels look at and educate themselves while reading through your code. Don&rsquo;t
  247. include filenames in log messages, Git provides that information.
  248. </p>
  249. <p>Possibly make the commit message have a terse, descriptive first line, an
  250. empty line and then a full description. The first line will be used to name
  251. the patch by <code>git format-patch</code>.
  252. </p>
  253. <a name="Preparing-a-patchset"></a>
  254. <h2 class="section"><a href="git-howto.html#toc-Preparing-a-patchset">2.10 Preparing a patchset</a></h2>
  255. <div class="example">
  256. <pre class="example">git format-patch &lt;commit&gt; [-o directory]
  257. </pre></div>
  258. <p>will generate a set of patches for each commit between <var>&lt;commit&gt;</var> and
  259. current <var>HEAD</var>. E.g.
  260. </p>
  261. <div class="example">
  262. <pre class="example">git format-patch origin/master
  263. </pre></div>
  264. <p>will generate patches for all commits on current branch which are not
  265. present in upstream.
  266. A useful shortcut is also
  267. </p>
  268. <div class="example">
  269. <pre class="example">git format-patch -n
  270. </pre></div>
  271. <p>which will generate patches from last <var>n</var> commits.
  272. By default the patches are created in the current directory.
  273. </p>
  274. <a name="Sending-patches-for-review"></a>
  275. <h2 class="section"><a href="git-howto.html#toc-Sending-patches-for-review">2.11 Sending patches for review</a></h2>
  276. <div class="example">
  277. <pre class="example">git send-email &lt;commit list|directory&gt;
  278. </pre></div>
  279. <p>will send the patches created by <code>git format-patch</code> or directly
  280. generates them. All the email fields can be configured in the global/local
  281. configuration or overridden by command line.
  282. Note that this tool must often be installed separately (e.g. <var>git-email</var>
  283. package on Debian-based distros).
  284. </p>
  285. <a name="Renaming_002fmoving_002fcopying-files-or-contents-of-files"></a>
  286. <h2 class="section"><a href="git-howto.html#toc-Renaming_002fmoving_002fcopying-files-or-contents-of-files">2.12 Renaming/moving/copying files or contents of files</a></h2>
  287. <p>Git automatically tracks such changes, making those normal commits.
  288. </p>
  289. <div class="example">
  290. <pre class="example">mv/cp path/file otherpath/otherfile
  291. git add [-A] .
  292. git commit
  293. </pre></div>
  294. <a name="Git-configuration"></a>
  295. <h1 class="chapter"><a href="git-howto.html#toc-Git-configuration">3 Git configuration</a></h1>
  296. <p>In order to simplify a few workflows, it is advisable to configure both
  297. your personal Git installation and your local FFmpeg repository.
  298. </p>
  299. <a name="Personal-Git-installation"></a>
  300. <h2 class="section"><a href="git-howto.html#toc-Personal-Git-installation">3.1 Personal Git installation</a></h2>
  301. <p>Add the following to your &lsquo;<tt>~/.gitconfig</tt>&rsquo; to help <code>git send-email</code>
  302. and <code>git format-patch</code> detect renames:
  303. </p>
  304. <div class="example">
  305. <pre class="example">[diff]
  306. renames = copy
  307. </pre></div>
  308. <a name="Repository-configuration"></a>
  309. <h2 class="section"><a href="git-howto.html#toc-Repository-configuration">3.2 Repository configuration</a></h2>
  310. <p>In order to have <code>git send-email</code> automatically send patches
  311. to the ffmpeg-devel mailing list, add the following stanza
  312. to &lsquo;<tt>/path/to/ffmpeg/repository/.git/config</tt>&rsquo;:
  313. </p>
  314. <div class="example">
  315. <pre class="example">[sendemail]
  316. to = ffmpeg-devel@ffmpeg.org
  317. </pre></div>
  318. <a name="FFmpeg-specific"></a>
  319. <h1 class="chapter"><a href="git-howto.html#toc-FFmpeg-specific">4 FFmpeg specific</a></h1>
  320. <a name="Reverting-broken-commits"></a>
  321. <h2 class="section"><a href="git-howto.html#toc-Reverting-broken-commits">4.1 Reverting broken commits</a></h2>
  322. <div class="example">
  323. <pre class="example">git reset &lt;commit&gt;
  324. </pre></div>
  325. <p><code>git reset</code> will uncommit the changes till <var>&lt;commit&gt;</var> rewriting
  326. the current branch history.
  327. </p>
  328. <div class="example">
  329. <pre class="example">git commit --amend
  330. </pre></div>
  331. <p>allows one to amend the last commit details quickly.
  332. </p>
  333. <div class="example">
  334. <pre class="example">git rebase -i origin/master
  335. </pre></div>
  336. <p>will replay local commits over the main repository allowing to edit, merge
  337. or remove some of them in the process.
  338. </p>
  339. <div class="float alert alert-info">
  340. <p><code>git reset</code>, <code>git commit --amend</code> and <code>git rebase</code>
  341. rewrite history, so you should use them ONLY on your local or topic branches.
  342. The main repository will reject those changes.
  343. </p></div>
  344. <div class="example">
  345. <pre class="example">git revert &lt;commit&gt;
  346. </pre></div>
  347. <p><code>git revert</code> will generate a revert commit. This will not make the
  348. faulty commit disappear from the history.
  349. </p>
  350. <a name="Pushing-changes-to-remote-trees"></a>
  351. <h2 class="section"><a href="git-howto.html#toc-Pushing-changes-to-remote-trees">4.2 Pushing changes to remote trees</a></h2>
  352. <div class="example">
  353. <pre class="example">git push origin master --dry-run
  354. </pre></div>
  355. <p>Will simulate a push of the local master branch to the default remote
  356. (<var>origin</var>). And list which branches and ranges or commits would have been
  357. pushed.
  358. Git will prevent you from pushing changes if the local and remote trees are
  359. out of sync. Refer to <a href="#Updating-the-source-tree-to-the-latest-revision">Updating the source tree to the latest revision</a>.
  360. </p>
  361. <div class="example">
  362. <pre class="example">git remote add &lt;name&gt; &lt;url&gt;
  363. </pre></div>
  364. <p>Will add additional remote with a name reference, it is useful if you want
  365. to push your local branch for review on a remote host.
  366. </p>
  367. <div class="example">
  368. <pre class="example">git push &lt;remote&gt; &lt;refspec&gt;
  369. </pre></div>
  370. <p>Will push the changes to the <var>&lt;remote&gt;</var> repository.
  371. Omitting <var>&lt;refspec&gt;</var> makes <code>git push</code> update all the remote
  372. branches matching the local ones.
  373. </p>
  374. <a name="Finding-a-specific-svn-revision"></a>
  375. <h2 class="section"><a href="git-howto.html#toc-Finding-a-specific-svn-revision">4.3 Finding a specific svn revision</a></h2>
  376. <p>Since version 1.7.1 Git supports &lsquo;<samp>:/foo</samp>&rsquo; syntax for specifying commits
  377. based on a regular expression. see man gitrevisions
  378. </p>
  379. <div class="example">
  380. <pre class="example">git show :/'as revision 23456'
  381. </pre></div>
  382. <p>will show the svn changeset &lsquo;<samp>r23456</samp>&rsquo;. With older Git versions searching in
  383. the <code>git log</code> output is the easiest option (especially if a pager with
  384. search capabilities is used).
  385. </p>
  386. <p>This commit can be checked out with
  387. </p>
  388. <div class="example">
  389. <pre class="example">git checkout -b svn_23456 :/'as revision 23456'
  390. </pre></div>
  391. <p>or for Git &lt; 1.7.1 with
  392. </p>
  393. <div class="example">
  394. <pre class="example">git checkout -b svn_23456 $SHA1
  395. </pre></div>
  396. <p>where <var>$SHA1</var> is the commit hash from the <code>git log</code> output.
  397. </p>
  398. <a name="Pre_002dpush-checklist"></a>
  399. <h1 class="chapter"><a href="git-howto.html#toc-Pre_002dpush-checklist">5 Pre-push checklist</a></h1>
  400. <p>Once you have a set of commits that you feel are ready for pushing,
  401. work through the following checklist to doublecheck everything is in
  402. proper order. This list tries to be exhaustive. In case you are just
  403. pushing a typo in a comment, some of the steps may be unnecessary.
  404. Apply your common sense, but if in doubt, err on the side of caution.
  405. </p>
  406. <p>First, make sure that the commits and branches you are going to push
  407. match what you want pushed and that nothing is missing, extraneous or
  408. wrong. You can see what will be pushed by running the git push command
  409. with &lsquo;<samp>--dry-run</samp>&rsquo; first. And then inspecting the commits listed with
  410. <code>git log -p 1234567..987654</code>. The <code>git status</code> command
  411. may help in finding local changes that have been forgotten to be added.
  412. </p>
  413. <p>Next let the code pass through a full run of our test suite.
  414. </p>
  415. <ul>
  416. <li> <code>make distclean</code>
  417. </li><li> <code>/path/to/ffmpeg/configure</code>
  418. </li><li> <code>make fate</code>
  419. </li><li> if fate fails due to missing samples run <code>make fate-rsync</code> and retry
  420. </li></ul>
  421. <p>Make sure all your changes have been checked before pushing them, the
  422. test suite only checks against regressions and that only to some extend. It does
  423. obviously not check newly added features/code to be working unless you have
  424. added a test for that (which is recommended).
  425. </p>
  426. <p>Also note that every single commit should pass the test suite, not just
  427. the result of a series of patches.
  428. </p>
  429. <p>Once everything passed, push the changes to your public ffmpeg clone and post a
  430. merge request to ffmpeg-devel. You can also push them directly but this is not
  431. recommended.
  432. </p>
  433. <a name="Server-Issues"></a>
  434. <h1 class="chapter"><a href="git-howto.html#toc-Server-Issues">6 Server Issues</a></h1>
  435. <p>Contact the project admins at <a href="mailto:root@ffmpeg.org">root@ffmpeg.org</a> if you have technical
  436. problems with the Git server.
  437. </p> </div>
  438. </body>
  439. </html>