Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] toolchain: add missing stamp file touch in external toolchain
Date: Thu, 23 Dec 2010 11:13:49 +0100	[thread overview]
Message-ID: <87ipyksso2.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <7f7c793bd9f7ee4b0745b35c9106cf16be717172.1293096662.git.thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Thu, 23 Dec 2010 10:31:08 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 Thomas> In the support of custom external toolchains, we forgot to touch the
 Thomas> $(STAMP_DIR)/ext-toolchain-checked stamp file, which means that the
 Thomas> toolchain was re-checked and re-installed at everyt build.

Committed, thanks.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2010-12-23 10:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23  9:31 [Buildroot] [pull request] Pull request for branch for-2011.02/fix-external-toolchain Thomas Petazzoni
2010-12-23  9:31 ` [Buildroot] [PATCH 1/1] toolchain: add missing stamp file touch in external toolchain Thomas Petazzoni
2010-12-23 10:13   ` 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=87ipyksso2.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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