All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] common: Makefile: 'cd' command could lead to broken default_env.h
Date: Tue, 23 Oct 2012 13:25:17 +0200	[thread overview]
Message-ID: <20121023112517.GA21425@pengutronix.de> (raw)
In-Reply-To: <20121023070455.GJ27665@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 685 bytes --]

On Tue, Oct 23, 2012 at 09:04:55AM +0200, Sascha Hauer wrote:
> On Mon, Oct 22, 2012 at 07:14:08PM +0200, Wolfram Sang wrote:
> > Depending on the user's settings (CDPATH), 'cd' may print out the
> > directory which was changed to. This causes broken barebox_default_env.h
> > to be generated. Ignore the cd printout.
> 
> I didn't know such a thing exists. This can cause unexpected behaviour
> of 'cd'. Wouldn't it be better to completely disable it by emptying
> CDPATH in scripts?

Yes, probably. You or me? :)

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2012-10-23 11:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 17:14 [PATCH] common: Makefile: 'cd' command could lead to broken default_env.h Wolfram Sang
2012-10-23  7:04 ` Sascha Hauer
2012-10-23 11:25   ` Wolfram Sang [this message]
2012-10-23 12:54     ` Sascha Hauer

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=20121023112517.GA21425@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.