* Alvaro Herrera <alvhe...@commandprompt.com> [090602 13:25]:

> That's not the problem.  The problem is that it is kept in the same
> directory as the checked out copy.  It would be a lot more usable if it
> was possible to store it elsewhere.
> 
> Yes, the .svn directories are a PITA.

You can export GIT_DIR to make the .git directory be somewhere else...
and you'll probalby want a corresponding GIT_WORK_TREE (or core.worktree
config) set.

If your careful (i.e. don't make a mistake), you can set GIT_DIR and
GIT_INDEX_FILE AND GIT_WORK_TREE, and use a single "git repository"
among multiple independent "working directories".

That said, is the carefulness needed to work that worth the < 200KB
you save?

On a "referenced" style development repository:
        moun...@pumpkin:~/pg-work/REL8_3_STABLE$ du -shc .git/*
        4.0K    .git/branches
        4.0K    .git/config
        4.0K    .git/description
        4.0K    .git/HEAD
        48K     .git/hooks
        328K    .git/index
        8.0K    .git/info
        36K     .git/logs
        16K     .git/objects
        4.0K    .git/packed-refs
        32K     .git/refs
        488K    total

488K total in the .git directory, 328K of that is the index.

a.

-- 
Aidan Van Dyk                                             Create like a god,
ai...@highrise.ca                                       command like a king,
http://www.highrise.ca/                                   work like a slave.

Attachment: signature.asc
Description: Digital signature

Reply via email to