From: Francois Beaufort <beaufort.francois@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ] Fix nit in HACKING instructions
Date: Wed, 20 Apr 2016 11:25:17 +0200 [thread overview]
Message-ID: <1461144317-20684-2-git-send-email-beaufort.francois@gmail.com> (raw)
In-Reply-To: <1461144317-20684-1-git-send-email-beaufort.francois@gmail.com>
---
HACKING | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/HACKING b/HACKING
index 28f1009..d93730d 100644
--- a/HACKING
+++ b/HACKING
@@ -146,12 +146,12 @@ backtraces, compiler errors, etc.
# git config format.subjectprefix "PATCH BlueZ"
-6) Add a cover letter when introducing a new feature explaning what problem
+7) Add a cover letter when introducing a new feature explaning what problem
you're trying to solve:
# git format-patch --cover-letter -M origin/master -o outgoing/
# edit outgoing/0000-*
-7) Submit:
+8) Submit:
# git send-email outgoing/*
--
2.7.0
next prev parent reply other threads:[~2016-04-20 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 9:25 [PATCH BlueZ] Fix nit in HACKING instructions Francois Beaufort
2016-04-20 9:25 ` Francois Beaufort [this message]
2016-04-22 12:06 ` Luiz Augusto von Dentz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1461144317-20684-2-git-send-email-beaufort.francois@gmail.com \
--to=beaufort.francois@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).