From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ncdu: bump to version 1.13
Date: Mon, 4 Feb 2019 09:57:07 +0100 [thread overview]
Message-ID: <20190204095707.5994e0e2@windsurf> (raw)
In-Reply-To: <1549198072-2967-1-git-send-email-gilles.talis@gmail.com>
Hello,
We now like to have commit titles that start with "package/<foo>", so I
fixed that.
On Sun, 3 Feb 2019 13:47:52 +0100
Gilles Talis <gilles.talis@gmail.com> wrote:
> +# computed locally
> +md5 6682a63e3e3e8ea14051d05056a857a0 COPYING
We use sha256 hashes for locally calculated hashes, so I've replaced by
such a hash instead.
Applied with those two changes. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-02-04 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 12:47 [Buildroot] [PATCH] ncdu: bump to version 1.13 Gilles Talis
2019-02-04 8:57 ` Thomas Petazzoni [this message]
2019-02-04 18:06 ` Gilles Talis
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=20190204095707.5994e0e2@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