All of lore.kernel.org
 help / color / mirror / Atom feed
From: redstun <redstun@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, Mike Gant <mike@gantsfort.com>
Subject: Re: [idea] separate .git dir and the working tree
Date: Sat, 5 Feb 2011 22:24:25 +0800	[thread overview]
Message-ID: <AANLkTinYMuXSvKjgtpSCbJPuo=PHDGR_OgOkwtV4Azmz@mail.gmail.com> (raw)
In-Reply-To: <20110205132708.GA18391@elie>

Making .git a symbol link is nice.

Regarding the GIT_DIR variable, looks like it needs to be paired with
the GIT_WORK_TREE variable, does this mean that I can only have one
local git repository?

what I wanted is, I may have multiple git working tree in my $HOME, like:
$HOME/proj1
$HOME/proj2,

I then wanted their .git directories respectively located at
/safe/disk/.git_proj1
/safe/disk/.git_proj2

How can I get this? I tried to read the doc but didn't have much luck.

Thanks

On Sat, Feb 5, 2011 at 9:27 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> (restoring cc list; please do not cull cc's)
>
> Mike Gant wrote:
>> On Sat, Feb 05, 2011 at 10:53:58AM +0800, redstun wrote:
>
>>> I think separating the .git directory from its working tree could
>>> increase the safety of the data to one more level higher.
> [...]
>> GIT_DIR and GIT_WORK_TREE might be what you are looking for. Explanation
>> of usage in 'man git'
>
> The .git directory is allowed to be a symlink.  Or a file like so
>
>        gitdir: /path/to/git/repo
>
> for symlink-challenged operating systems.  See gitrepository-layout(7)
> for details.
>
> Cheers,
> Jonathan
>

  reply	other threads:[~2011-02-05 14:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-05  2:53 [idea] separate .git dir and the working tree redstun
2011-02-05  3:23 ` Mike Gant
2011-02-05 13:27   ` Jonathan Nieder
2011-02-05 14:24     ` redstun [this message]
2011-02-05 18:04       ` Jonathan Nieder
2011-02-06  0:20     ` Mike Gant
2011-02-06  0:40       ` Mike Gant
2011-02-06  1:00         ` Jared Hance
2011-02-06 10:49           ` Konstantin Khomoutov
2011-02-06 10:55         ` [idea] " Nicolas Sebrecht
2011-02-07  4:57           ` Mike Gant
2011-05-23 14:40         ` [idea] " Michael Witten

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='AANLkTinYMuXSvKjgtpSCbJPuo=PHDGR_OgOkwtV4Azmz@mail.gmail.com' \
    --to=redstun@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=mike@gantsfort.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.