git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jay Soffian" <jaysoffian+git@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Johannes Sixt" <j.sixt@viscovery.net>,
	git@vger.kernel.org, "Lars Hjemli" <hjemli@gmail.com>
Subject: Re: [PATCH] allow setting GIT_WORK_TREE to "no work tree"
Date: Thu, 7 Feb 2008 02:13:39 -0500	[thread overview]
Message-ID: <76718490802062313jdbd0e84xc9f36d703bb86c44@mail.gmail.com> (raw)
In-Reply-To: <20080207051317.GA32296@sigill.intra.peff.net>

On Feb 7, 2008 12:13 AM, Jeff King <peff@peff.net> wrote:
>
> On Wed, Feb 06, 2008 at 12:59:32PM -0800, Junio C Hamano wrote:
> >
> > I was tempted to suggest GIT_WORK_TREE=/dev/null because that is
> > what "diff" uses to mark "this does not even exist", but that
> > feels dirty.
>
> It feels dirty to me, too. I would rather choose something that doesn't
> even look like a path. I think GIT_WORK_TREE=" " is too ugly, too.

Is using something like "__GIT_WORK_TREE_NOT_SET__" that terrible?

j.

  reply	other threads:[~2008-02-07  7:14 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
2008-02-06 20:59       ` Junio C Hamano
2008-02-07  5:13         ` Jeff King
2008-02-07  7:13           ` Jay Soffian [this message]
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=76718490802062313jdbd0e84xc9f36d703bb86c44@mail.gmail.com \
    --to=jaysoffian+git@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hjemli@gmail.com \
    --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).