projects / git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ed44fd0) | patch
Documentation: explain how to check for patch corruption
authorJonathan Nieder <jrnieder@gmail.com>
Fri, 15 Apr 2011 02:24:01 +0000 (21:24 -0500)
committerJunio C Hamano <gitster@pobox.com>
Fri, 15 Apr 2011 20:28:03 +0000 (13:28 -0700)
commit57756161eed50f2b52c9e32b01f6388814a09943
treeb313b6b5d8c65f90e077787755b944f11ad7cb25tree | snapshot
parented44fd045a8a4bcf7f30a47e4fc6aba761faaf78commit | diff
Documentation: explain how to check for patch corruption

SubmittingPatches has some excellent advice about how to check a patch
for corruption before sending it off.  Move it to the format-patch
manual so it can be installed with git's documentation for use by
people not necessarily interested in the git project's practices.

Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/SubmittingPatches diff | blob | blame | history
Documentation/git-format-patch.txt diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.