From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] separate .git from working directory
Date: Wed, 11 Oct 2006 16:41:03 +0200 [thread overview]
Message-ID: <81b0412b0610110741q698e6512xc8a4188bac0294a4@mail.gmail.com> (raw)
In-Reply-To: <fcaeb9bf0610110623q365d3ffcw9ba9e11936d03a9d@mail.gmail.com>
On 10/11/06, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
> Hi,
> I was thinking about this while reading subproject thread. In a simple
> case, I have a repo A located at ~/project-a and another repo B
> located at ~/project-a/some/dir/project-b. With this setup, command
> "find" and other directory-recursive commands will run horribly from
> ~/project-a when they go inside project-b/.git (no I don't want to
> repack -d everytime I want to find something).
> I propose to move project-b/.git outside and place a file, say
> .gitdir, in project-b directory. git-sh-setup and setup_git_directory
You can even leave the name as is: it is impossible to misunderstand
a file for directory (except on AIX). Or put the information in extended
attributes.
next prev parent reply other threads:[~2006-10-11 14:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 13:23 [RFC] separate .git from working directory Nguyen Thai Ngoc Duy
2006-10-11 14:41 ` Alex Riesen [this message]
[not found] ` <20061011184844.40b1205d.seanlkml@sympatico.ca>
2006-10-11 22:48 ` Sean
[not found] ` <20061011114303.0a23496e.seanlkml@sympatico.ca>
2006-10-11 15:43 ` Sean
2006-10-11 21:55 ` Nguyen Thai Ngoc Duy
2006-10-12 4:07 ` Liu Yubao
2006-10-12 5:04 ` Liu Yubao
2006-10-11 18:14 ` Martin Waitz
2006-10-11 21:46 ` Nguyen Thai Ngoc Duy
2006-10-11 22:22 ` Junio C Hamano
2006-10-12 5:21 ` Martin Waitz
2006-10-21 17:08 ` Nguyen Thai Ngoc Duy
-- strict thread matches above, loose matches on Subject: below --
2006-10-12 12:15 Sergio Callegari
2006-10-12 13:03 ` Alex Riesen
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=81b0412b0610110741q698e6512xc8a4188bac0294a4@mail.gmail.com \
--to=raa.lkml@gmail.com \
--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 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).