summaryrefslogtreecommitdiff
path: root/Documentation/SubmittingPatches
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2014-12-22 12:26:38 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2014-12-22 12:26:38 -0800
commit63296d583ca107b3f590c3a09be9b3670a2c1afb (patch)
tree10f96a3e2b756b11ae1d8c014b584d69131b06a0 /Documentation/SubmittingPatches
parentMerge branch 'tb/config-core-filemode-check-on-broken-fs' (diff)
parentt/README: justify why "! grep foo" is sufficient (diff)
downloadtgif-63296d583ca107b3f590c3a09be9b3670a2c1afb.tar.xz
Merge branch 'jc/refer-to-t-readme-from-submitting-patches'
* jc/refer-to-t-readme-from-submitting-patches: t/README: justify why "! grep foo" is sufficient SubmittingPatches: refer to t/README for tests
Diffstat (limited to 'Documentation/SubmittingPatches')
-rw-r--r--Documentation/SubmittingPatches3
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index fa71b5f0b6..e3c942e579 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -57,7 +57,8 @@ change, the approach taken by the change, and if relevant how this
differs substantially from the prior version, are all good things
to have.
-Make sure that you have tests for the bug you are fixing.
+Make sure that you have tests for the bug you are fixing. See
+t/README for guidance.
When adding a new feature, make sure that you have new tests to show
the feature triggers the new behaviour when it should, and to show the