All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Carlos Martín Nieto" <carlos@cmartin.tk>
Cc: John Twilley <mathuin@gmail.com>, git@vger.kernel.org
Subject: Re: BUG: "--work-tree blah" does not imply "--git-dir blah/.git" or fix misleading error message
Date: Wed, 30 Nov 2011 12:45:41 -0800	[thread overview]
Message-ID: <7v1uspqqyy.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20111130194233.GD12096@centaur.lab.cmartin.tk> ("Carlos Martín Nieto"'s message of "Wed, 30 Nov 2011 20:42:33 +0100")

Carlos Martín Nieto <carlos@cmartin.tk> writes:

> On Wed, Nov 30, 2011 at 11:21:29AM -0800, Junio C Hamano wrote:
>> subdirectory "blah/.git"), but I do not think this is likely to change, as
>> I suspect that people and scripts are relying on the current behaviour to
>> be able to do something like this:
>> 
>>     cd /pub/scm/git/git.git ;# this is a bare repository
>>     mkdir /var/tmp/git
>>     git --work-tree=/var/tmp/git checkout
>
> This is in fact the way that many (or from what I can see the most
> popular) tutorials for abusing git as a deployment system tell you to
> run it (though more often than not setting GIT_WORKTREE in the
> environment).

Heh, *ab*using is a good description if they really mean to use it as a
deployment system. For one thing it won't do anything a proper deployment
should do if the target directory is not empty ;-)

      reply	other threads:[~2011-11-30 20:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30 17:43 BUG: "--work-tree blah" does not imply "--git-dir blah/.git" or fix misleading error message John Twilley
2011-11-30 18:22 ` Carlos Martín Nieto
2011-11-30 19:13   ` John Twilley
2011-12-01 14:30     ` Carlos Martín Nieto
2011-11-30 19:21 ` Junio C Hamano
2011-11-30 19:42   ` Carlos Martín Nieto
2011-11-30 20:45     ` Junio C Hamano [this message]

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=7v1uspqqyy.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=carlos@cmartin.tk \
    --cc=git@vger.kernel.org \
    --cc=mathuin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.