Could you write a small explanation in the message body. Also, I would
prefer that the title has a prefix and that you add a Fixes trailer
referencing the commit that introduced the typo. Something like:
readme: fix typo in contribution guide
git: 'sendemail' is not a git command. See 'git --help'.
The most similar command is
send-email
Fixes: b84374a572b4 ("readme: add contribution guide")
Signed-off-by: inwit <inwit@sindominio.net>
Thanks!
diff --git a/README.md b/README.md
index 71f382c..338d9c2 100644
--- a/README.md+++ b/README.md
@@ -105,12 +105,12 @@ defaults:
And send the patch to the mailing list:
- $ git sendemail --annotate -1+ $ git send-email --annotate -1Wait for feedback. Address comments and amend changes to your original commit.
Then you should send a v2:
- $ git sendemail --in-reply-to=$first_message_id --annotate -v2 -1+ $ git send-email --in-reply-to=$first_message_id --annotate -v2 -1Once the maintainer is happy with your patch, they will apply it and push it.
--
2.32.0
git: 'sendemail' is not a git command. See 'git --help'.
The most similar command is
send-email
Fixes: b84374a572b4 ("readme: add contribution guide")
Signed-off-by: inwit <inwit@sindominio.net>
To git.sr.ht:~rjarry/aerc
e58194c7b515..50b0436510b0 master -> master
Thanks!
---
README.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 71f382c..338d9c2 100644
--- a/README.md+++ b/README.md
@@ -105,12 +105,12 @@ defaults:
And send the patch to the mailing list:
- $ git sendemail --annotate -1+ $ git send-email --annotate -1Wait for feedback. Address comments and amend changes to your original commit.
Then you should send a v2:
- $ git sendemail --in-reply-to=$first_message_id --annotate -v2 -1+ $ git send-email --in-reply-to=$first_message_id --annotate -v2 -1Once the maintainer is happy with your patch, they will apply it and push it.
--
2.32.0