Skip to content
This repository
Browse code

[ffmpeg] updated and reformated ffmpeg/patches/README-patches

  • Loading branch information...
commit 1d26033f55c430bdc40f64dc201521216635b8f3 1 parent c403dcf
authored April 19, 2013

Showing 1 changed file with 15 additions and 4 deletions. Show diff stats Hide diff stats

  1. 19  lib/ffmpeg/patches/README-patches
19  lib/ffmpeg/patches/README-patches
... ...
@@ -1,7 +1,18 @@
1  
-This directory contains XBMC custom patches that are refactored to fit the FFmpeg n1.2 rev e820e3a distribution. 
  1
+This directory contains XBMC custom patches that are refactored to fit the FFmpeg
  2
+n1.2 rev e820e3a distribution. 
2 3
 
3  
-All patches in the patches folder are already applied to the ffmpeg code base and are only kept here for tracking history. Some of patches are ours and some are backports from ffmpegs upstream. Patches that has become obsolete since ffmpeg n0.10.2 are moved to obsolete-patches, also for tracking reasons.
  4
+All patches in the patches folder are already applied to the ffmpeg code base and
  5
+are only kept here for tracking history. Some of patches are ours and some are
  6
+backports from ffmpegs upstream. Patches that has become obsolete since ffmpeg
  7
+n0.10.2 are moved to obsolete-patches, also for tracking reasons.
4 8
 
5  
-Normally you can have a look into that patchfile itself to see if its a backport or not (we normally leave the original commit message and the committer in there). You can also use "git log lib/ffmpeg/patches" to show the history where the patch file came from.
  9
+Normally you can have a look into that patchfile itself to see if its a backport
  10
+or not (we normally leave the original commit message and the committer in there).
  11
+You can also use "git log lib/ffmpeg/patches" to show the history where the patch
  12
+file came from.
6 13
 
7  
-Whenever you need to patch a new ffmpeg versions you apply the patch and then add the git diff to the patches folder in the next commit (if its a backport - adapt the patch so that it clearly states that it is a change from upstream and which commit in ffmpeg repo it is).
  14
+Whenever you need to patch a new ffmpeg versions you apply the patch and then add
  15
+the git diff to the patches folder in the next commit (if its a backport - adapt
  16
+the patch so that it clearly states that it is a change from upstream and which
  17
+commit in ffmpeg repo it is). Please use an uniq patch number this check that
  18
+the number doesn't conflict with others in obsolete patches.

0 notes on commit 1d26033

Please sign in to comment.
Something went wrong with that request. Please try again.