From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] monit: bump to version 3.12.2
Date: Thu, 16 Apr 2015 07:59:28 +0200 [thread overview]
Message-ID: <20150416075928.7b0a7a3a@free-electrons.com> (raw)
In-Reply-To: <1429129390-28278-1-git-send-email-sebastien.bourdelin@savoirfairelinux.com>
Dear Sebastien Bourdelin,
On Wed, 15 Apr 2015 16:23:10 -0400, Sebastien Bourdelin wrote:
> Also add hash file and remove the m4 directory creation from the monit.mk
> which is now in the source tree.
>
> Signed-off-by: Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com>
> ---
> package/monit/monit.hash | 6 ++++++
> package/monit/monit.mk | 8 +-------
> 2 files changed, 7 insertions(+), 7 deletions(-)
> create mode 100644 package/monit/monit.hash
Applied after keeping only the upstream sha256 in the hash file, as
suggested by Baruch, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-04-16 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 20:23 [Buildroot] [PATCH 1/1] monit: bump to version 3.12.2 Sebastien Bourdelin
2015-04-16 3:25 ` Baruch Siach
2015-04-16 5:59 ` 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=20150416075928.7b0a7a3a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox