From: "Yakov Lerner" <iler.ml@gmail.com>
To: git@vger.kernel.org
Subject: GIT_DIR question
Date: Sun, 17 Jun 2007 18:34:14 +0300 [thread overview]
Message-ID: <f36b08ee0706170834m464ce57dl3fd5b549b23abb16@mail.gmail.com> (raw)
In-Reply-To: <f36b08ee0706170829w59979d86i7bf09bc35ff28fca@mail.gmail.com>
I wanted to create cloned repo, but with metaninfo separately from data.
I cloned the repo ( git-clone ~/repo ~/x) ,
then I moved ~/x/.git to different place (mv ~/x/.git ~/git);
then exported GIT_DIR=~/git; then
cd ~/x;
But now 'git status' says 'fatal: runstatus must be run in a work tree' . Why ?
'ls $GIT_DIR' shows
FETCH_HEAD HEAD ORIG_HEAD branches config
description hooks index info logs objects refs
This is ok, no ?
Thanks
Yakov
next parent reply other threads:[~2007-06-17 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f36b08ee0706170829w59979d86i7bf09bc35ff28fca@mail.gmail.com>
2007-06-17 15:34 ` Yakov Lerner [this message]
2007-06-17 21:52 ` GIT_DIR question Matthias Lederhofer
2007-06-18 19:43 ` Yakov Lerner
2007-06-19 7:15 ` Matthias Lederhofer
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=f36b08ee0706170834m464ce57dl3fd5b549b23abb16@mail.gmail.com \
--to=iler.ml@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.
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).