git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Yubao <yubao.liu@gmail.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Sean <seanlkml@sympatico.ca>, git@vger.kernel.org
Subject: Re: [RFC] separate .git from working directory
Date: Thu, 12 Oct 2006 12:07:58 +0800	[thread overview]
Message-ID: <452DBF9E.7010900@gmail.com> (raw)
In-Reply-To: <fcaeb9bf0610111455y225237cmdbaadbf294686d8e@mail.gmail.com>

Nguyen Thai Ngoc Duy wrote:
> On 10/11/06, Sean <seanlkml@sympatico.ca> wrote:
>> You can export a GIT_DIR manually pretty easily if you want to move
>> the .git directory somewhere else.  Also you could make a "git find"
>> shell script named "gf" that does something like:
>>
>> #/bin/sh
>> find "$@" ! -path '*/.git/*'
>>
>> Which would let you type  "gf -name blah" and automatically ignore
>> the .git directory.
> 
> It should work. However I would rather use "normal" find than
> specialized ones. Imagine somedays I hate find and start to love grep,
> I would have to find out --exclude option and create new "gg" script.
> In worse cases where recursive commands don't support filtering, I
> have no chance to filter out .git directories.
> 
Subversion puts a .svn/ in every directory under control, I dislike this
feature, I have to use many wrapper scripts.

Maybe the svk way is worth considering, it maintains a map relation
between paths in repository and file system like this:

$ svk checkout --list
           depot path			path
==================================================================
//path/in/repos/hello/world.c           /path/in/fs/hello/world.c

The problem is users must maintain this map when move or delete
/path/in/fs/hello/world.c, it's a bit annoying.

see http://svkbook.elixus.org/nightly/en/svk-book.html#svk.ref.svk.c.checkout
for more information.

  reply	other threads:[~2006-10-12  4:08 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
     [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 [this message]
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=452DBF9E.7010900@gmail.com \
    --to=yubao.liu@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    --cc=seanlkml@sympatico.ca \
    /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).