From: "Shawn O. Pearce" <spearce@spearce.org>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git <git@vger.kernel.org>
Subject: Re: git's is_inside_git_dir too strict?
Date: Wed, 7 Mar 2007 10:53:07 -0500 [thread overview]
Message-ID: <20070307155307.GC27596@spearce.org> (raw)
In-Reply-To: <fcaeb9bf0703070417n5d3fb168jc7efd4642ad38c92@mail.gmail.com>
Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
> On 3/7/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> >Well, there is a real problem with "This operation must be run in a work
> >tree". What operation is that? We tried to make it hard to overwrite
> >things in $GIT_DIR by running Git operations meant for the working tree,
> >and it seems like you are running one of them.
>
> From this command:
>
> git --git-dir=/home/pclouds/blog/data.git ls-files --others --modified
> 2007-03-07T18_52_41.txt
>
> It was run in /home/pclouds/blog/data, which is the working directory
> of data.git.
Why not just symlink it?
cd /home/pclouds/blog/data
ln -s ../data.git .git
But really, why is your Git repository for the working directory
outside of the working directory? Why not just move data.git to
data/.git ?
--
Shawn.
next prev parent reply other threads:[~2007-03-07 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 15:41 git's is_inside_git_dir too strict? Nguyen Thai Ngoc Duy
2007-03-06 21:46 ` Johannes Schindelin
2007-03-07 12:17 ` Nguyen Thai Ngoc Duy
2007-03-07 15:53 ` Shawn O. Pearce [this message]
2007-03-07 16:12 ` Nguyen Thai Ngoc Duy
2007-03-09 12:00 ` Matthias Lederhofer
2007-03-10 1:11 ` Junio C Hamano
2007-03-10 11:49 ` Nguyen Thai Ngoc Duy
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=20070307155307.GC27596@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=pclouds@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.