Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] minicom: add COPYING sha256 to hash
Date: Thu, 27 Sep 2018 22:28:17 +0200	[thread overview]
Message-ID: <8736tuadni.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180831105600.70955-1-giulio.benetti@micronovasrl.com> (Giulio Benetti's message of "Fri, 31 Aug 2018 12:55:59 +0200")

>>>>> "Giulio" == Giulio Benetti <giulio.benetti@micronovasrl.com> writes:

 > In minicom package hash file lacks sha256 entry for COPYING file even if
 > it is added to MINICOM_LICENSE_FILES.

 > Add COPYING sha256 entry to minicom.hash file.

 > Signed-off-by: Giulio Benetti <giulio.benetti@micronovasrl.com>

Committed to 2018.02.x and 2018.05.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2018-09-27 20:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31 10:55 [Buildroot] [PATCH 1/2] minicom: add COPYING sha256 to hash Giulio Benetti
2018-08-31 10:56 ` [Buildroot] [PATCH 2/2] minicom: bump version Giulio Benetti
2018-08-31 12:13   ` Thomas Petazzoni
2018-08-31 13:32     ` Giulio Benetti
2018-08-31 13:38     ` [Buildroot] [PATCH v2 1/2] minicom: add COPYING sha256 to hash Giulio Benetti
2018-08-31 13:38       ` [Buildroot] [PATCH v2 2/2] minicom: bump version Giulio Benetti
2018-08-31 21:47         ` Thomas Petazzoni
2018-08-31 22:29           ` Giulio Benetti
2018-09-01  7:18             ` Thomas Petazzoni
2018-08-31 21:32       ` [Buildroot] [PATCH v2 1/2] minicom: add COPYING sha256 to hash Thomas Petazzoni
2018-09-27 20:28 ` Peter Korsgaard [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=8736tuadni.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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