Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Suykov <alex.suykov@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2 v4] vboot-utils: new package
Date: Thu, 24 Dec 2015 21:26:02 +0200	[thread overview]
Message-ID: <20151224192602.GA14377@vostro> (raw)
In-Reply-To: <20151224185516.GO25803@vapier.lan>

Thu, Dec 24, 2015 at 01:55:16PM -0500, Mike Frysinger wrote:

> this seems to have the same errors i pointed out in the ealier versions

(this message I think:
http://lists.busybox.net/pipermail/buildroot/2015-December/146493.html )

"ChromiumOS" instead of "Chromium OS" in Config.host.in, overlooked that.
This is going into v5 patch then.

As for the tarball issue, I don't think there are any better options.
It's either that, or a git checkout.
Do you mean it would be better to use git instead?

  reply	other threads:[~2015-12-24 19:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-24 18:43 [Buildroot] [PATCH 1/2 v4] vboot-utils: new package Alex Suykov
2015-12-24 18:55 ` Mike Frysinger
2015-12-24 19:26   ` Alex Suykov [this message]
2016-01-02  6:16     ` Mike Frysinger

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=20151224192602.GA14377@vostro \
    --to=alex.suykov@gmail.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