From: Dave Chinner <david@fromorbit.com>
To: Lucas Stach <dev@lynxeye.de>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] progs: use make provided CURDIR instead of rolling our own
Date: Wed, 2 Sep 2015 06:04:48 +1000 [thread overview]
Message-ID: <20150901200448.GK26895@dastard> (raw)
In-Reply-To: <1441131010-5439-1-git-send-email-dev@lynxeye.de>
On Tue, Sep 01, 2015 at 08:10:10PM +0200, Lucas Stach wrote:
> This fixes broken header symlinks when make isn't triggered from the xfsprogs
> source location, but as a recursion from another make in a different
> directory. This is a common pattern found in cross build systems.
It should actually use TOPDIR to be consistent with the result of
the makefiles. i.e. all paths are relative to TOPDIR, not PWD or
CURDIR.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-09-01 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 18:10 [PATCH] progs: use make provided CURDIR instead of rolling our own Lucas Stach
2015-09-01 20:04 ` Dave Chinner [this message]
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=20150901200448.GK26895@dastard \
--to=david@fromorbit.com \
--cc=dev@lynxeye.de \
--cc=xfs@oss.sgi.com \
/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