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 1/1] emlog: new package
Date: Fri, 18 Dec 2015 17:07:09 +0100	[thread overview]
Message-ID: <20151218170709.43ddaabd@free-electrons.com> (raw)
In-Reply-To: <1450446298-3523-1-git-send-email-joris.lijssens@gmail.com>

Joris,

On Fri, 18 Dec 2015 14:44:58 +0100, Joris Lijssens wrote:
> Signed-off-by: Joris Lijssens <joris.lijssens@gmail.com>
> ---
>  package/Config.in        |  1 +
>  package/emlog/Config.in  | 12 ++++++++++++
>  package/emlog/emlog.hash |  2 ++
>  package/emlog/emlog.mk   | 21 +++++++++++++++++++++
>  4 files changed, 36 insertions(+)
>  create mode 100644 package/emlog/Config.in
>  create mode 100644 package/emlog/emlog.hash
>  create mode 100644 package/emlog/emlog.mk

I guess this is a new version of the emlog patch, right?

If so, a new iteration should be labeled as "PATCH v2" and should carry
a changelog. See
https://buildroot.org/downloads/manual/manual.html#submitting-patches.

This helps us a lot to understand what has changed between the
different iterations of a patch.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-12-18 16:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18 13:44 [Buildroot] [PATCH 1/1] emlog: new package Joris Lijssens
2015-12-18 16:07 ` Thomas Petazzoni [this message]
2015-12-20 16:06 ` Arnout Vandecappelle
2015-12-21 22:52 ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2015-12-04 10:22 [Buildroot] [PATCH 1/1] emlog:new package Joris Lijssens
2015-12-17 21:42 ` Yann E. MORIN

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=20151218170709.43ddaabd@free-electrons.com \
    --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.