From: Cristian Ionescu-Idbohrn <cristian.ionescu-idbohrn@axis.com>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] $(STAGING_DIR)/include -> $(STAGING_DIR)/usr/include
Date: Mon, 30 Jul 2007 21:19:38 +0200 (CEST) [thread overview]
Message-ID: <0707302118120.17391@somehost> (raw)
In-Reply-To: <0707302108520.17391@somehost>
On Mon, 30 Jul 2007, Cristian Ionescu-Idbohrn wrote:
> Whitespace-cleanup too.
> --includedir=/include -> --includedir=/usr/include and similar with
> $(STAGING_DIR) mixed in there.
As the previous post was refused for being too large, here is a zipped
version.
Cheers,
--
Cristian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: br.mk.patch.gz
Type: application/octet-stream
Size: 5360 bytes
Desc:
Url : http://busybox.net/lists/buildroot/attachments/20070730/4caa7f95/attachment.obj
next prev parent reply other threads:[~2007-07-30 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 19:13 [Buildroot] [patch] $(STAGING_DIR)/include -> $(STAGING_DIR)/usr/include Cristian Ionescu-Idbohrn
2007-07-30 19:19 ` Cristian Ionescu-Idbohrn [this message]
2007-07-30 19:47 ` Bernhard Fischer
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=0707302118120.17391@somehost \
--to=cristian.ionescu-idbohrn@axis.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