From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] a5c48a: Fix loglevel for steps in companion tools
Date: Tue, 24 Jan 2017 22:27:00 -0000 [thread overview]
Message-ID: <5887d4ad4c03d_27ef3f87a051f13c879a9@hookshot-fe6-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: a5c48a5d0a6c46f139bc531f68e4fe430b2cd07f
https://github.com/crosstool-ng/crosstool-ng/commit/a5c48a5d0a6c46f139bc531f68e4fe430b2cd07f
Author: Alexey Neyman <stilor@att.net>
Date: 2017-01-23 (Mon, 23 Jan 2017)
Changed paths:
M scripts/build/companion_tools/050-make.sh
M scripts/build/companion_tools/100-m4.sh
M scripts/build/companion_tools/200-autoconf.sh
M scripts/build/companion_tools/300-automake.sh
M scripts/build/companion_tools/400-libtool.sh
Log Message:
-----------
Fix loglevel for steps in companion tools
(was EXTRA, should be INFO to be consistent with the rest).
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 9061763a73c38032c1d889256f27929368381069
https://github.com/crosstool-ng/crosstool-ng/commit/9061763a73c38032c1d889256f27929368381069
Author: Alexey Neyman <stilor@att.net>
Date: 2017-01-24 (Tue, 24 Jan 2017)
Changed paths:
M scripts/build/companion_tools/050-make.sh
M scripts/build/companion_tools/100-m4.sh
M scripts/build/companion_tools/200-autoconf.sh
M scripts/build/companion_tools/300-automake.sh
M scripts/build/companion_tools/400-libtool.sh
Log Message:
-----------
Merge pull request #554 from stilor/comptools-loglevel
Fix loglevel for steps in companion tools
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/48bb11145de6...9061763a73c3
reply other threads:[~2017-01-24 22:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5887d4ad4c03d_27ef3f87a051f13c879a9@hookshot-fe6-cp1-prd.iad.github.net.mail \
--to=stilor@att.net \
--cc=crossgcc@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).