From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [v2] eigen: (optionally) install unsupported modules
Date: Tue, 18 Mar 2014 23:52:02 +0100 [thread overview]
Message-ID: <20140318235202.202ac1ab@skate> (raw)
In-Reply-To: <1395173894-4811-1-git-send-email-zinosat@tiscali.it>
Dear Davide Viti,
On Tue, 18 Mar 2014 21:18:13 +0100, Davide Viti wrote:
> I'm working on a package that includes some files inside the
> "unsupported" folder. The unsupported modules can be optionally
> selected.
>
> Let's see if I can manage to properly send a signed patch with
> introductory message: sorry for the noise!
Almost :-)
For a single patch, there is no real need to send a separate
introduction message, the patch itself is enough.
To indicate the new version, you should generate the patch as follows:
git format-patch --suject-prefix="PATCHv2" HEAD^
so that the patch title becomes:
[PATCHv2] title of the patch
You manually added [v2] to the title of your introduction e-mail, but
it's actually more important to have it on the patches themselves. And
don't do it manually, use git --subject-prefix option to do it!
See
http://buildroot.org/downloads/manual/manual.html#_patch_revision_changelog
for more details.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-03-18 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 20:18 [Buildroot] [v2] eigen: (optionally) install unsupported modules Davide Viti
2014-03-18 20:18 ` [Buildroot] [PATCH] " Davide Viti
2014-03-18 22:55 ` Thomas Petazzoni
2014-03-19 7:25 ` Samuel Martin
2014-03-19 8:07 ` Davide Viti
2014-03-19 17:11 ` Thomas Petazzoni
2014-03-18 22:52 ` Thomas Petazzoni [this message]
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=20140318235202.202ac1ab@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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