aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDiego Biurrun <diego@biurrun.de>2012-10-25 18:25:25 +0200
committerDiego Biurrun <diego@biurrun.de>2012-10-26 18:28:38 +0200
commitca7f59119b8a53d60418c4adccb0c46922795f79 (patch)
tree7ac6b57e055ad8b2533e5972434d633d714284b7
parent87cdd7c6949e0166a22b558e0657ac277c95d452 (diff)
downloadffmpeg-ca7f59119b8a53d60418c4adccb0c46922795f79.tar.gz
doc: git-howto: Clarify comment about pushing series of commits
-rw-r--r--doc/git-howto.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/git-howto.texi b/doc/git-howto.texi
index 51141157c1..68e0061d74 100644
--- a/doc/git-howto.texi
+++ b/doc/git-howto.texi
@@ -416,8 +416,8 @@ a panacea. Do not hesitate to perform any other tests necessary to convince
yourself that the changes you are about to push actually work as expected.
Also note that every single commit should pass the test suite, not just
-the result of a series of patches. So if you have a series of related
-commits, run the test suite on every single commit.
+the result of a series of patches. So if you have a series of commits
+to push, run the test suite on every single commit.
Finally, after pushing, mark all patches as committed on
@url{http://patches.libav.org/,patchwork}.