From: Junio C Hamano <junkio@cox.net>
To: Carl Baldwin <cnb@fc.hp.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] unset CDPATH in git-clone
Date: Mon, 05 Sep 2005 12:37:58 -0700 [thread overview]
Message-ID: <7v3boj486h.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20050901152441.GA8694@hpsvcnb.fc.hp.com
Carl Baldwin <cnb@fc.hp.com> writes:
> The function get_repo_base seems to break with this CDPATH.
Sorry, your message somehow slipped my filtering. Thanks for
the analysis. Of course, CDPATH would break it.
Is there any good reason why somebody would want to have CDPATH
in his environment, inherited to be used by any shell scripts,
as opposed to have it as a plain shell variable that is set only
in interactive shells? I do not think of any.
next prev parent reply other threads:[~2005-09-05 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 15:24 [PATCH] unset CDPATH in git-clone Carl Baldwin
2005-09-05 19:37 ` Junio C Hamano [this message]
2005-09-06 14:52 ` Carl Baldwin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v3boj486h.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=cnb@fc.hp.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).