From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/manual: fixing one liners for vagrant
Date: Sun, 7 Feb 2016 13:40:45 +0100 [thread overview]
Message-ID: <1454848845-22149-1-git-send-email-angelo.compagnucci@gmail.com> (raw)
* Changing back wget to curl cause wget it's not available
on mac os x.
* Braking up too long windows one liner.
Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
---
docs/manual/getting.txt | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/docs/manual/getting.txt b/docs/manual/getting.txt
index bb63cab..549938a 100644
--- a/docs/manual/getting.txt
+++ b/docs/manual/getting.txt
@@ -19,13 +19,15 @@ If you want to setup an isolated buildroot environment on Linux or Mac
Os X, paste this line onto your terminal:
--------------------
-wget https://buildroot.org/downloads/Vagrantfile; vagrant up
+curl -O https://buildroot.org/downloads/Vagrantfile; vagrant up
--------------------
If you are on Windows, paste this into your powershell:
--------------------
-(new-object System.Net.WebClient).DownloadFile("https://buildroot.org/downloads/Vagrantfile","Vagrantfile"); vagrant up
+(new-object System.Net.WebClient).DownloadFile(
+"https://buildroot.org/downloads/Vagrantfile","Vagrantfile");
+vagrant up
--------------------
If you want to follow development, you can use the daily snapshots or
--
1.9.1
next reply other threads:[~2016-02-07 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 12:40 Angelo Compagnucci [this message]
2016-02-07 23:22 ` [Buildroot] [PATCH] docs/manual: fixing one liners for vagrant Arnout Vandecappelle
2016-02-08 10:12 ` Angelo Compagnucci
2016-02-08 12:34 ` Thomas Petazzoni
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=1454848845-22149-1-git-send-email-angelo.compagnucci@gmail.com \
--to=angelo.compagnucci@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