Re: [libav-devel] [PATCH] doc: git-howto: Clarify comment about pushing series of commits
On 10/26/12 12:03 PM, Diego Biurrun wrote: --- doc/git-howto.texi |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/git-howto.texi b/doc/git-howto.texi index 5114115..68e0061 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}. Ok, might be useful to provide a git filter branch to run such task. ___ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
[libav-devel] [PATCH] doc: git-howto: Clarify comment about pushing series of commits
--- doc/git-howto.texi |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/git-howto.texi b/doc/git-howto.texi index 5114115..68e0061 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}. -- 1.7.1 ___ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel