From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Johannes Sixt <j.sixt@viscovery.net>, git@vger.kernel.org
Subject: Re: [PATCH] allow setting GIT_WORK_TREE to "no work tree"
Date: Wed, 06 Feb 2008 12:54:01 -0800 [thread overview]
Message-ID: <7v4pclvmae.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080206110131.GA4167@coredump.intra.peff.net> (Jeff King's message of "Wed, 6 Feb 2008 06:01:32 -0500")
Jeff King <peff@peff.net> writes:
> On Wed, Feb 06, 2008 at 11:42:15AM +0100, Johannes Sixt wrote:
>
>> > The special value is a blank GIT_WORK_TREE; it could be any
>> > value, but this should not conflict with any user values
>> > (and as a bonus, you can now tell git "I don't have a work
>> > tree" with "GIT_WORK_TREE= git", though I suspect the use
>> > case for that is limited).
>>
>> Hrm. Unfortunately, on Windows there is no such thing as an empty
>> environment string. setenv(x, "") *removes* the environment variable.
>
> Bleh. Maybe "GIT_WORK_TREE=:"? It doesn't make sense by itself since we
> don't try to execute the contents of GIT_WORK_TREE, but it's unlikely to
> be used by a user, and I believe there was recent talk of making
> "GIT_EDITOR=:" work.
>
> The other option is setting
>
> GIT_MAGICALLY_SET_GIT_DIR_SO_DONT_ACT_LIKE_THE_USER_DID=1
>
> but I was hoping to avoid that.
Yuck. Let's then try your original (slightly redundant) one.
next prev parent reply other threads:[~2008-02-06 20:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 10:26 [PATCH] allow setting GIT_WORK_TREE to "no work tree" Jeff King
2008-02-06 10:42 ` Johannes Sixt
2008-02-06 11:01 ` Jeff King
2008-02-06 20:54 ` Junio C Hamano [this message]
2008-02-06 20:59 ` Junio C Hamano
2008-02-07 5:13 ` Jeff King
2008-02-07 7:13 ` Jay Soffian
2008-02-07 12:33 ` Johannes Schindelin
2008-02-07 18:06 ` Jay Soffian
2008-02-07 9:10 ` Junio C Hamano
2008-02-07 19:02 ` Johannes Schindelin
2008-02-08 7:21 ` Johannes Sixt
2008-02-08 12:05 ` Johannes Schindelin
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=7v4pclvmae.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=peff@peff.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;
as well as URLs for NNTP newsgroup(s).