From: "Christian MICHON" <christian.michon@gmail.com>
To: git <git@vger.kernel.org>
Subject: GIT_DIR used to work with git-1.4.4.4
Date: Fri, 18 May 2007 16:24:44 +0200 [thread overview]
Message-ID: <46d6db660705180724n43dfeebakf5725a04e5b10673@mail.gmail.com> (raw)
sorry if I created too much (user) noise around this issue, but
this is mostly why as a user I refrained using git-1.5.x
I sometimes have a scm work flow where I'd like to have my
GIT_DIR sitting on another file system, so therefore not in
the current working directory.
I used to be able to do this in git-1.4.4.4:
(it's a rather useless example, I know)
mkdir /home/xian/vault
export GIT_DIR=/home/xian/vault
mkdir /tmp/xianwork
cd /tmp/xianwork
touch a b
git init-db
git add .
This was truly working, and now using git-1.5.1.4, it's not.
Instead I get: "fatal: add must be run in a work tree"
from the source code, I understand what to change if I
want to get the old behavior.
My questions are:
- is this new behavior truly needed ?
- is there another way to do this using newer work flow ?
( I know already about the symbolic .git link trick )
Thanks in advance for any useful tips.
--
Christian
reply other threads:[~2007-05-18 14:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46d6db660705180724n43dfeebakf5725a04e5b10673@mail.gmail.com \
--to=christian.michon@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