public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Brüns, Stefan" <Stefan.Bruens@rwth-aachen.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] git send-email and patch headers/subject line
Date: Tue, 4 Oct 2016 15:10:42 +0000	[thread overview]
Message-ID: <4071091.fENbyqzKdz@sbruens-linux> (raw)
In-Reply-To: <CAOLEWZWi7Fct+cygirKqkkHnmM9rqcswQdOx7mwcN3_DiXet9Q@mail.gmail.com>

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

  reply	other threads:[~2016-10-04 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04  0:02 [U-Boot] git send-email and patch headers/subject line Stephen Arnold
2016-10-04 15:10 ` Brüns, Stefan [this message]
2016-10-04 17:59   ` Stephen Arnold

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=4071091.fENbyqzKdz@sbruens-linux \
    --to=stefan.bruens@rwth-aachen.de \
    --cc=u-boot@lists.denx.de \
    /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