From: Bryan Hundven <bryanhundven@gmail.com>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 12d24e: functions: Softlink custom directory
Date: Tue, 09 Feb 2016 00:10:00 -0000 [thread overview]
Message-ID: <56b92e6be9ff5_40673f7fb862b2a012121@hookshot-fe5-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 12d24ee33b6c8bddd534db57b683d839f6df2fb9
https://github.com/crosstool-ng/crosstool-ng/commit/12d24ee33b6c8bddd534db57b683d839f6df2fb9
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2016-02-08 (Mon, 08 Feb 2016)
Changed paths:
M scripts/functions
Log Message:
-----------
functions: Softlink custom directory
Hardlinking the custom source directory does not work across separate
mount points. Chnage this to a softlink instead.
This closes #336
Reported-by: Jasmin Jessich <jasmin@anw.at>
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
Commit: b1c319da4598b2060e27c6d2618d85fd93ccd203
https://github.com/crosstool-ng/crosstool-ng/commit/b1c319da4598b2060e27c6d2618d85fd93ccd203
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2016-02-08 (Mon, 08 Feb 2016)
Changed paths:
M scripts/functions
Log Message:
-----------
Merge pull request #337 from bhundven/softlink_custom_directory
functions: Softlink custom directory
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/1cfc160f9d18...b1c319da4598
[-- Attachment #2: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
reply other threads:[~2016-02-09 0:10 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=56b92e6be9ff5_40673f7fb862b2a012121@hookshot-fe5-cp1-prd.iad.github.net.mail \
--to=bryanhundven@gmail.com \
--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).