From: Junio C Hamano <junkio@cox.net>
To: Greg Louis <glouis@dynamicro.on.ca>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Redirect cd output to /dev/null, was: git-clone seems dead
Date: Mon, 12 Sep 2005 12:53:13 -0700 [thread overview]
Message-ID: <7v3boaawra.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20050912163637.GA22018@athame.dynamicro.on.ca
Greg Louis <glouis@dynamicro.on.ca> writes:
> Or (2+1==3) detect CDPATH in the same places as (1), complain with a
> brief explanation ("don't export CDPATH; it's really only useful in
> interactive shells") and unset it.
I like your wording above, so probably that is what is going to
happen. Thanks for the suggestion.
> My patch was about the equivalent of (1), and (1) is what I'd feel
> was the most that git owes its users.
CDPATH has two problems. 1. It takes scripts to unexpected
places (somebody had CDPATH=..:../..:$HOME and the "cd" in
git-clone.sh:get_repo_base took him to $HOME/.git when he said
"clone foo bar" to clone a repository in "foo" which had
"foo/.git"). CDPATH mechanism does not implicitly give "." at
the beginning of CDPATH, which is the most irritating part.
2. the extra echo when it does its thing.
I was under the impression that the patch fixed 2. without doing
anything about 1., but I may be mistaken.
> Option (0) could be justified on the grounds that git users
> are presumably developers and ought to be able to catch that
> sort of blunder, but the facts that you didn't originally twig
> to it, and that it took me a couple of hours to find it
> independently, suggest that that's too cavalier an attitude
> (neither of us being a tyro).
Maybe. I did not trigger it and did not immediately spot what
was wrong when I heard the symptom because I do not use CDPATH
anywhere myself -- I am old fashioned ;-).
next prev parent reply other threads:[~2005-09-12 19:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 18:13 git-clone seems dead Peter Eriksen
2005-09-11 19:04 ` Junio C Hamano
2005-09-11 22:04 ` Greg Louis
2005-09-11 23:01 ` [PATCH] Redirect cd output to /dev/null, was: " Greg Louis
2005-09-12 1:47 ` Junio C Hamano
2005-09-12 9:22 ` Peter Eriksen
2005-09-12 10:56 ` Greg Louis
2005-09-12 12:29 ` Junio C Hamano
2005-09-12 16:36 ` Greg Louis
2005-09-12 19:53 ` Junio C Hamano [this message]
2005-09-13 11:07 ` Greg Louis
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=7v3boaawra.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=glouis@dynamicro.on.ca \
/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 NNTP newsgroup(s).