From: "Steven Rostedt (VMware)" <rostedt@xxxxxxxxxxx> There's two hyphens in the CONTRIBUTE file before send-email, which do not belong. Get rid of them. Signed-off-by: Steven Rostedt (VMware) <rostedt@xxxxxxxxxxx> --- CONTRIBUTE | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTE b/CONTRIBUTE index aed78110..0440b186 100644 --- a/CONTRIBUTE +++ b/CONTRIBUTE @@ -67,12 +67,12 @@ fix that makes the code harder to read, that fix can probably be ignored. Finally, you can use the git "send-email" functionality: - git --send-email --from='<your-email> --to='linux-trace-devel@xxxxxxxxxxxxxxx' HEAD~1..HEAD + git send-email --from='<your-email> --to='linux-trace-devel@xxxxxxxxxxxxxxx' HEAD~1..HEAD If you are sending one patch, if you are adding more than one patch, also include a cover letter: - git --send-email --cover-letter --annotate --from='<your-email> --to='linux-trace-devel@xxxxxxxxxxxxxxx' <first-commit>~1..HEAD + git send-email --cover-letter --annotate --from='<your-email> --to='linux-trace-devel@xxxxxxxxxxxxxxx' <first-commit>~1..HEAD If you receive feedback on your patches, and plan on sending another version, please use the '-v' option to mark your patches that they are a new version. @@ -80,7 +80,7 @@ For example, if you add "-v2" to the above commands, instead of having: "[PATCH]" in the subject, it will have "[PATCH v2]", letting the reviewers know that this is a new version. If you send another version, use "-v3" and so on. -For more information about git --send-email: +For more information about git send-email: https://git-scm.com/docs/git-send-email -- 2.29.2
|