@end example
+@chapter Git configuration
+
+In order to simplify a few workflows, it is advisable to configure both
+your personal Git installation and your local Libav repository.
+
+@section Personal Git installation
+
+Add the following to your @file{~/.gitconfig} to help @command{git send-email}
+and @command{git format-patch} detect renames:
+
+@example
+[diff]
+ renames = copy
+@end example
+
+@section Repository configuration
+
+In order to have @command{git send-email} automatically send patches
+to the libav-devel mailing list, add the following stanza
+to @file{/path/to/libav/repository/.git/config}:
+
+@example
+[sendemail]
+ to = libav-devel@@libav.org
+@end example
+
@chapter Libav specific
@section Reverting broken commits
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.
+
+Give other developers a reasonable amount of time to look at and review
+patches before you push them. Not everybody is online 24/7, but may wish
+to look at and comment on a patch nonetheless. The time you leave depends
+on the urgency and complexity of the patch. Use your common sense to pick
+a timeframe that allows everybody that you think may wish to comment
+and/or should comment on the change an opportunity to see it.
Finally, after pushing, mark all patches as committed on
@url{http://patches.libav.org/,patchwork}.