From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Choose xz compressed tarball for linux kernel.
Date: Sat, 11 May 2013 12:11:55 +0200 [thread overview]
Message-ID: <20130511121155.0377f81f@skate> (raw)
In-Reply-To: <201305110104.51488.rasasi78@gmail.com>
Dear Ra?l S?nchez Siles,
On Sat, 11 May 2013 01:04:51 +0200, Ra?l S?nchez Siles wrote:
> Hi:
>
> This is a retry of previous patch, now inlined as requested. Patch is the same
> as before so no patch version increased.
>
> I wanted to apologize to Jerzy for my abrupt appearance: I had this patch
> working some time ago and it was standing in my "to send" queue. I was also
> willing to contribute buildroot somehow.
>
> Regards,
>
> Signed-off-by: Ra?l S?nchez Siles <rasasi78@gmail.com>
> ---
> linux/linux.mk | 2 +-
> toolchain/kernel-headers/kernel-headers.mk | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
Thanks, but your commit log shouldn't contain "personal messages". It
should contain a description of what the patch is. Basically, anything
that's before the "---" remains forever in the Git history of
Buildroot. If you want to put "personal" messages, or a changelog, or
anything like that, please put it after the "---", or in a separate
e-mail that serves as a cover letter.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-11 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 23:04 [Buildroot] [PATCH] Choose xz compressed tarball for linux kernel Raúl Sánchez Siles
2013-05-11 10:11 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-11 11:40 Raúl Sánchez Siles
2013-05-11 12:02 ` Thomas Petazzoni
2013-05-11 20:44 ` Peter Korsgaard
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=20130511121155.0377f81f@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