2016-04-20 09:25:16

by François Beaufort

Subject: [PATCH BlueZ] Fix nit in HACKING instructions

Francois Beaufort (1):
Fix nit in HACKING instructions

HACKING | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

--
2.7.0

2016-04-22 12:06:06

by Luiz Augusto von Dentz

Subject: Re: [PATCH BlueZ] Fix nit in HACKING instructions

Hi Francois,

On Wed, Apr 20, 2016 at 12:25 PM, Francois Beaufort
<[email protected]> wrote:
> ---
> 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

Applied, thanks.

--
Luiz Augusto von Dentz

2016-04-20 09:25:17

by François Beaufort

Subject: [PATCH BlueZ] Fix nit in HACKING instructions

---
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