Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Pedro Aguilar <paguilar@paguilar.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libunistring: bump version to 1.0
Date: Sat, 22 Jan 2022 13:19:51 +0100	[thread overview]
Message-ID: <20220122131951.2846f704@windsurf> (raw)
In-Reply-To: <20220119223208.1196891-1-paguilar@paguilar.org>

On Wed, 19 Jan 2022 23:32:08 +0100
Pedro Aguilar <paguilar@paguilar.org> wrote:

> - Update indentation in hash file (two spaces)

I'm not sure what went wrong, but between "sha256" and the hash, you
had a tab and not two spaces, so "check-package" was complaining.

I fixed that when applying to master. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-01-22 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 22:32 [Buildroot] [PATCH 1/1] package/libunistring: bump version to 1.0 Pedro Aguilar
2022-01-22 12:19 ` 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=20220122131951.2846f704@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=paguilar@paguilar.org \
    /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