SubmittingPatches « Documentation - git.git - The core git plumbing

Submitting Patches ================== == Guidelines Here are some guidelines for contributing back to this project. There is also a link:MyFirstContribution.html[step-by-step tutorial] available which covers many of these same guidelines. [[patch-flow]] === A typical life cycle of a patch series To help us understand the reason behind various guidelines given later in the document, first let's und

[Nyoho]

命令法で書けと書いてある。Describe your changes in imperative mood, e.g. "make xyzzy do frotz"instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy to do frotz", as if you are giving orders to the codebase to change its behavior. without external

[mogwaing]

“Describe your changes in imperative mood, e.g. "make xyzzy do frotz" instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy to do frotz", as if you are giving orders to the codebase to change its behaviour. ”

[morygonzalez]

三単現のs無しの現在形の動詞で commit log を書けと書いてある。

[ita-wasa]

12 - the body should provide a meaningful commit message, which: 13 - uses the imperative, present tense: "change", 14 not "changed" or "changes". 15 - includes motivation for the change, and contrasts 16 its implementation