All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libconfuse: bump to version 2.7 take 4
Date: Thu, 1 Sep 2011 09:26:21 +0200	[thread overview]
Message-ID: <20110901092621.4a77e73c@skate> (raw)
In-Reply-To: <4E5207B1.7000409@ethertek.ca>

Hello Dan,

Le Mon, 22 Aug 2011 00:39:29 -0700,
Dan Pattison <dan.pattison@ethertek.ca> a ?crit :

> Sorry for multiple patch submissions. I think I got it right this time.

It is almost right, except for this sentence. Basically, in your email,
everything that is above the --- marker (just below your Signed-off-by
line) becomes the commit log that gets stored for the eternity in the
project history. Therefore, we typically don't include "personal"
messages such as this one.

If you really want to add a personal message, put it between the ---
marker and the beginning of the patch itself.

Could you repost a new version with this fixed ?

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-09-01  7:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18 23:53 [Buildroot] [PATCH] libconfuse: bump to version 2.7 Dan Pattison
2011-08-19  4:48 ` [Buildroot] [PATCH] libconfuse: bump to version 2.7 take 2 Dan Pattison
2011-08-19  9:06   ` Thomas Petazzoni
2011-08-19 15:12     ` [Buildroot] [PATCH] libconfuse: bump to version 2.7 take 3 Dan Pattison
2011-08-22  7:39       ` [Buildroot] [PATCH] libconfuse: bump to version 2.7 take 4 Dan Pattison
2011-09-01  7:26         ` Thomas Petazzoni [this message]
2011-09-01 14:47         ` [Buildroot] [PATCH] libconfuse: bump to version 2.7 take 5 Dan Pattison
2011-09-11 13:15           ` Peter Korsgaard
2011-09-11 15:41             ` Dan Pattison
2011-09-11 17:55               ` 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=20110901092621.4a77e73c@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.