From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
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 23:12:57 +0700 [thread overview]
Message-ID: <fcaeb9bf0703070812y27425b07pf78fbdf14898b360@mail.gmail.com> (raw)
In-Reply-To: <20070307155307.GC27596@spearce.org>
On 3/7/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
> > 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
It's currently my workaround.
> 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 ?
The directory "data" is automatically manipulated by scripts. I feel
it safer for data.git being outside of data so if I make any mistake,
data.git _might_ remain intact. You see, if I link data/.git to
data.git, my scripts' bugs might affect data.git too.
> --
> Shawn.
>
--
Duy
next prev parent reply other threads:[~2007-03-07 16:13 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
2007-03-07 16:12 ` Nguyen Thai Ngoc Duy [this message]
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=fcaeb9bf0703070812y27425b07pf78fbdf14898b360@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).