From: Andreas Schwab <schwab@linux-m68k.org>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: GIT_DIR vs. --git-dir
Date: Mon, 24 Sep 2012 15:37:18 +0200 [thread overview]
Message-ID: <m2zk4fa6ep.fsf@igel.home> (raw)
In-Reply-To: <5060588D.3080202@drmicha.warpmail.net> (Michael J. Gruber's message of "Mon, 24 Sep 2012 14:56:45 +0200")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> But that argument applies to config files in exactly the same way as it
> applies to command line arguments. Git is the only one reading them. So
> why not leave it up to Git to decide about expansion?
Command line arguments are first processed by the shell, handling
expansions like $HOME. It is part of the Unix philosophy that expansion
of command lines is left to the shell.
> On the other hand: If Git expanding arguments is surprising, why is it
> unsurprising if Git expands config values?
The config file is not processed by the shell.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-09-24 13:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 7:19 GIT_DIR vs. --git-dir Michael J Gruber
2012-09-24 7:41 ` Nguyen Thai Ngoc Duy
2012-09-24 7:57 ` Michael J Gruber
2012-09-24 9:53 ` Nguyen Thai Ngoc Duy
2012-09-24 12:56 ` Michael J Gruber
2012-09-24 12:57 ` [RFC/PATCH] git: expand user path in --git-dir Michael J Gruber
2012-09-24 14:52 ` Jeff King
2012-09-24 14:57 ` Michael J Gruber
2012-09-24 17:30 ` Junio C Hamano
2012-09-25 5:33 ` Jan Engelhardt
2012-09-25 7:27 ` Michael J Gruber
2012-09-24 13:37 ` Andreas Schwab [this message]
2012-09-24 14:36 ` GIT_DIR vs. --git-dir Junio C Hamano
2012-09-24 14:51 ` Michael J Gruber
2012-09-24 14:49 ` Jeff King
2012-09-24 14:54 ` Michael J Gruber
2012-09-24 15:42 ` Andreas Schwab
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=m2zk4fa6ep.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.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;
as well as URLs for NNTP newsgroup(s).