From: Paul Jones <paul.jones@iwtech.com.au>
To: buildroot@busybox.net
Subject: [Buildroot] Resume on WGET commands
Date: Wed, 17 Mar 2010 18:59:55 +1100 [thread overview]
Message-ID: <4BA08BFB.4080102@iwtech.com.au> (raw)
Is there a reason that buildroot doesn't seem to use the -c command for
wget by default? It would be quite handy to have.
Then I remembered there was an option to modify the wget command line in
build options and it didn't seem to work.
Paul.
next reply other threads:[~2010-03-17 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 7:59 Paul Jones [this message]
2010-03-19 15:16 ` [Buildroot] Resume on WGET commands Peter Korsgaard
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=4BA08BFB.4080102@iwtech.com.au \
--to=paul.jones@iwtech.com.au \
--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.