From: Peter Korsgaard <jacmet@sunsite.dk>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] source: print messages when all sources downloaded
Date: Wed, 13 Jul 2011 08:37:26 +0200 [thread overview]
Message-ID: <87r55ufzyx.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1310512066-11450-3-git-send-email-yann.morin.1998@anciens.enib.fr> (Yann E. MORIN's message of "Wed, 13 Jul 2011 01:07:46 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@anciens.enib.fr> writes:
Yann> When downloading all sources for later off-line build (eg. make source),
Yann> and the toolchain backend is crosstool-NG, the last messages the user
Yann> wil see is something like:
Yann> [INFO ] Retrieving needed toolchain components' tarballs: done in 98.02s (at 01:39)
Yann> [INFO ] Build completed at 20110713.000605
Yann> [INFO ] (elapsed: 1:39.21)
Yann> [INFO ] Finishing installation (may take a few seconds)...
Yann> which is pretty uninformative, here; crosstool-NG is just saying that
Yann> it just finished what it was asked for, that is download the sources,
Yann> but there is no separate message for that.
Yann> To avoid confusion, add an explicit message that makes it clear that
Yann> downloading the sources was sucessful, and nothing more.
I agree it isn't optimal, but this breaks E.G. make external-deps
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-07-13 6:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 23:07 [Buildroot] [PATCH 0/2] Allow only downloading sources with crosstool-NG backend Yann E. MORIN
2011-07-12 23:07 ` [Buildroot] [PATCH 1/2] toolchain/crosstool-ng: allow pre-downloading the sources Yann E. MORIN
2011-07-13 6:36 ` Peter Korsgaard
2011-07-12 23:07 ` [Buildroot] [PATCH 2/2] source: print messages when all sources downloaded Yann E. MORIN
2011-07-13 6:37 ` Peter Korsgaard [this message]
2011-07-13 18:11 ` Yann E. MORIN
2011-07-13 18:42 ` Peter Korsgaard
2011-07-13 20:46 ` Yann E. MORIN
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=87r55ufzyx.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--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