From: Dan Zwell <dzwell@gmail.com>
To: Dmitry Kakurin <dmitry.kakurin@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: $GIT_DIR usage
Date: Sun, 05 Aug 2007 08:22:54 -0400 [thread overview]
Message-ID: <46B5C11E.4000101@gmail.com> (raw)
In-Reply-To: <678E8953ECEB4B72A99DEA2137B05823@ntdev.corp.microsoft.com>
Dmitry Kakurin wrote:
> I think you also need to set GIT_WORK_TREE.
> This way Git will know the root of directories that it controls.
>
> - Dmitry
> ----- Original Message ----- From: "Dan Zwell" <dzwell@gmail.com>
> Newsgroups: gmane.comp.version-control.git
> To: <git@vger.kernel.org>
> Sent: Sunday, 5 August 2007 2:58
> Subject: $GIT_DIR usage
>
>
>> Hi, I had a question about $GIT_DIR. That is to say, it doesn't seem
>> to work. I am using Git 1.5.2.4. See the following: (all the commands
>> I tried besides "git-init" failed).
>>
>> $ export GIT_DIR="`pwd`/.git_public"
>> $ git init
>> warning: templates not found /usr/share//git-core/templates/
>> Initialized empty Git repository in /home/user/temp/.git_public/
>> $ echo > new_file
>> $ git add new_file
>> fatal: add must be run in a work tree
>> $ git commit -a
>> fatal: /usr/bin/git-commit cannot be used without a working tree.
>> $ git commit
>> fatal: /usr/bin/git-commit cannot be used without a working tree.
>> $
>>
>> Is $GIT_DIR not meant to be used this way? Does it have a different
>> purpose / use case, or is this just a bug?
>>
>> Thanks,
>> Dan
>
Thank you. I also had to upgrade Git to the as-yet unreleased version
(this variable doesn't exist in the current stable release), but what
you said makes sense and seems like it should work.
Dan
next prev parent reply other threads:[~2007-08-05 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 9:58 $GIT_DIR usage Dan Zwell
2007-08-05 11:55 ` Dmitry Kakurin
2007-08-05 12:22 ` Dan Zwell [this message]
2007-08-05 12:33 ` Johannes Schindelin
2007-08-05 13:02 ` Dan Zwell
2007-08-05 13:41 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46B5C11E.4000101@gmail.com \
--to=dzwell@gmail.com \
--cc=dmitry.kakurin@gmail.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).