From: "Mike Gant" <mike@gantsfort.com>
To: git@vger.kernel.org
Subject: Re: [idea] separate .git dir and the working tree
Date: Fri, 4 Feb 2011 20:23:39 -0700 [thread overview]
Message-ID: <20110205032339.GA15303@mg1> (raw)
In-Reply-To: <AANLkTik4MjnpOzPdGy7ZDiH0in4e1DpjrhQFOHjUiEEE@mail.gmail.com>
On Sat, Feb 05, 2011 at 10:53:58AM +0800, redstun wrote:
> First please shout if this is a known feature :-)
>
> I think separating the .git directory from its working tree could
> increase the safety of the data to one more level higher.
>
> We might have a git variable set to specify (a shared place) where to
> put the .git directories (or the data inside it), then use
> "/path/to/working/tree" as (or the seed to calculate) a hash key to
> map from the (.git directory in the) shared place to the working tree
> directory.
>
> Or we may have just a few data (that can be re-created) stored in the
> .git directory along with the working tree, and most of the revision
> history stored in the shared place.
GIT_DIR and GIT_WORK_TREE might be what you are looking for. Explanation
of usage in 'man git'
HTH
Mike
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-05 3:33 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 [this message]
2011-02-05 13:27 ` Jonathan Nieder
2011-02-05 14:24 ` redstun
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=20110205032339.GA15303@mg1 \
--to=mike@gantsfort.com \
--cc=git@vger.kernel.org \
/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).