git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git's is_inside_git_dir too strict?

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Mar 7, 2007, 16:12 UTC
Message-ID
<fcaeb9bf0703070812y27425b07pf78fbdf14898b360@mail.gmail.com>
In-Reply-To
<20070307155307.GC27596@spearce.org>
On 3/7/07, Shawn O. Pearce <spearce@spearce.org> wrote:
Show 8 quoted lines
> 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
Previous: Shawn O. PearceNext: Matthias Lederhofer
Message 5 of 8 in “git's is_inside_git_dir too strict?”
  1. Nguyen Thai Ngoc DuyMar 6, 2007
  2. Johannes SchindelinMar 6, 2007
  3. Nguyen Thai Ngoc DuyMar 7, 2007
  4. Shawn O. PearceMar 7, 2007
  5. Nguyen Thai Ngoc DuyMar 7, 2007
  6. Matthias LederhoferMar 9, 2007
  7. Junio C HamanoMar 10, 2007
  8. Nguyen Thai Ngoc DuyMar 10, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.