From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?iso-8859-1?Q?Br=FCns=2C_Stefan?= <Stefan.Bruens@rwth-aachen.de>
Date: Tue, 4 Oct 2016 15:10:42 +0000
Subject: [U-Boot] git send-email and patch headers/subject line
In-Reply-To: <CAOLEWZWi7Fct+cygirKqkkHnmM9rqcswQdOx7mwcN3_DiXet9Q@mail.gmail.com>
References: <CAOLEWZWi7Fct+cygirKqkkHnmM9rqcswQdOx7mwcN3_DiXet9Q@mail.gmail.com>
Message-ID: <4071091.fENbyqzKdz@sbruens-linux>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Montag, 3. Oktober 2016 17:02:37 CEST Stephen Arnold wrote:
> Howdy:
> 
> I could swear this worked the last time I sent patches to the OE list
> (at least it didn't need the gmail insecure app workaround so I guess
> it was a while ago).
> 
> Anyway, the real commit msg starts with ARM, I git format-patch and
> this time didn't touch the patches, then:
> 
> git send-email --to=test at lists.denx.de --confirm=always -M -1
> --subject-prefix="U-Boot][PATCH v3"  outgoing/*

You should *not* add the [U-Boot] tag to the message, this is done by the 
mailinglist software.

The wiki states to use:
$> git format-patch --subject-prefix="PATCH v2"

Current git allows a simpler variant, "--reroll-count", or short "-v":
$> git format-patch -v 2


"git send-email" has no "--subject-prefix" nor "-M" nor "-<n>" option. Just 
use
$> git send-email --to=<xxx> --cc <yyy> outgoing/*

Formatting and sending patches are two independent steps. You can't apply/copy 
options from one command to the other.

Prior to sending the patch, you *should* edit the 0000-cover-letter.patch.

Kind regards,

Stefan