Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/mender-artifact: bump version to 3.0.0
Date: Sat, 1 Jun 2019 14:09:52 +0200	[thread overview]
Message-ID: <20190601140952.6e301698@windsurf> (raw)
In-Reply-To: <20190528133927.30396-1-deinok@deinok.com>

Hello Raul,

On Tue, 28 May 2019 15:39:27 +0200
deinok at deinok.com wrote:

> From: Raul Hidalgo Caballero <deinok@deinok.com>
> 
> Signed-off-by: Raul Hidalgo Caballero <deinok@deinok.com>
> ---
>  package/mender-artifact/mender-artifact.hash | 2 +-
>  package/mender-artifact/mender-artifact.mk   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

So, I have applied to next, but I had to fix license file hashes: two
were incorrect. Also, a new license file should have been added. Please
make sure to run "make legal-info" after bumping a package, to make
sure the license information is still correct.

See the final commit at:

  https://git.buildroot.org/buildroot/commit/?h=next&id=069e6de63fc252fd7add9763c76bb61de954ec1f

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-06-01 12:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-28 13:39 [Buildroot] [PATCH 1/1] package/mender-artifact: bump version to 3.0.0 deinok at deinok.com
2019-06-01 12:09 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-05-28  8:52 deinok at deinok.com
2019-05-28 12:06 ` Thomas Petazzoni
2019-05-28 12:13   ` Raul Hidalgo Caballero
2019-05-28 12:24     ` Thomas Petazzoni
2019-05-28 18:29       ` Arnout Vandecappelle
2019-05-27  7:59 Raul Hidalgo Caballero
2019-05-27  9:12 ` Thomas Petazzoni

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=20190601140952.6e301698@windsurf \
    --to=thomas.petazzoni@bootlin.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