All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] DOWNLOAD: change $1=DIRECTORY_URL, $2=FILE_NAME to $1=FULL_FILE_URL, $2=FILE_NAME
Date: Sun, 18 Mar 2012 22:36:20 +0100	[thread overview]
Message-ID: <87bontlhgr.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1331905375-9177-1-git-send-email-alvaro.gamez@hazent.com> (Alvaro G. M.'s message of "Fri, 16 Mar 2012 14:42:53 +0100")

>>>>> "Alvaro" == Alvaro G M <alvaro.gamez@hazent.com> writes:

 Alvaro> From: "Alvaro G. M" <alvaro.gamez@hazent.com>

 Alvaro> This modifies the definition of DOWNLOAD to receive two
 Alvaro> arguments: the first one is the full URL of the file to
 Alvaro> download, whereas the second (and optional) is the name the
 Alvaro> file will have once downloaded.

 Alvaro> Same thing with the SOURCE_CHECK_WGET and SCP functions.

 Alvaro> All calls to these functions have been changed to the shortest
 Alvaro> form of the new API, except for toolchains acquisition. Since
 Alvaro> there is quite a number of different toolchains this call to
 Alvaro> DOWNLOAD is better set to the generic one.

Committed, thanks.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2012-03-18 21:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 13:42 [Buildroot] [PATCH 1/3] DOWNLOAD: change $1=DIRECTORY_URL, $2=FILE_NAME to $1=FULL_FILE_URL, $2=FILE_NAME Alvaro G. M
2012-03-16 13:42 ` [Buildroot] [PATCH 2/3] Microblaze: added architecture support for both big endian and low endian Alvaro G. M
2012-03-18 21:52   ` Peter Korsgaard
2012-03-16 13:42 ` [Buildroot] [PATCH 3/3] Microblaze: added external toolchain from Xilinx Alvaro G. M
2012-03-18 21:54   ` Peter Korsgaard
2012-03-18 17:54 ` [Buildroot] [PATCH 1/3] DOWNLOAD: change $1=DIRECTORY_URL, $2=FILE_NAME to $1=FULL_FILE_URL, $2=FILE_NAME Arnout Vandecappelle
2012-03-18 21:36 ` Peter Korsgaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-03-17  9:37 Stephan Hoffmann

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=87bontlhgr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.