projects / git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: eeff891) | patch
SubmittingPatches: refer to t/README for tests
authorJunio C Hamano <gitster@pobox.com>
Mon, 24 Nov 2014 17:43:29 +0000 (09:43 -0800)
committerJunio C Hamano <gitster@pobox.com>
Mon, 24 Nov 2014 17:43:29 +0000 (09:43 -0800)
commit54cc5d29a0590c47c6f32d15c867c0199fdd672a
treef7f2eb1c31ce7bc0a18a3cc87c86ab4b8b71d6b9tree | snapshot
parenteeff891ac756fd97a05476446f15269b714ce4cccommit | diff
SubmittingPatches: refer to t/README for tests

There are general guidelines for writing good tests in t/README
but neither SubmittingPatches nor CodingGuidelines refers to it,
which makes the document easy to be missed.

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