From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Paul Drews <paul.drews@intel.com>
Cc: git@vger.kernel.org
Subject: Re: rebase not honoring core.worktree pointing elsewhere
Date: Wed, 3 Nov 2010 07:13:58 +0700 [thread overview]
Message-ID: <AANLkTi=T5kHfgNOpOtCDCoq7epEgwUrVayaUCbf35dSU@mail.gmail.com> (raw)
In-Reply-To: <loom.20101102T165800-486@post.gmane.org>
On Tue, Nov 2, 2010 at 11:26 PM, Paul Drews <paul.drews@intel.com> wrote:
> BTW, the impetus for this is a big integrated cross-compilation build system
> that has a nasty habit of deleting and re-creating a chroot environment
> containing the directory structures including the work tree. If the ".git"
> dir is at the "normal" place "inside" the work tree, it gets deleted along
> with all the work I have done. Not good, which is why I want to keep the
> ".git" somewhere else that's safe. Solutions to this:
>
> (preferred) core.worktree pointing into worktree elsewhere, run all git
> commands from GIT_DIR. Would be great if rebase worked under these
> circumstances.
>
> (best fallback) no core.worktree, export GIT_DIR pointing elsewhere, run all
> git commands from unmarked root of worktree.
>
> (complex) A complex scenario pushing and pulling stuff between a git repo
> inside the worktree and another git clone outside the worktree.
>
> (implementation dependent) Having the ".git" dir inside the worktree be a
> symbolic link to a dir somewhere outside the work tree. Keeps the actual ".git"
> contents safe from deletion. Works so far, but this is Tampering With The
> Implementation in a way that is likely to fail down the road somewhere,
> e.g., if an internal script does cd to the GIT_DIR, then cd relative to
> that to try to get back into somewhere else in the work tree.
Another one: create a .git file with this line and put it in worktree's topdir
gitdir: /path/to/real/git.dir
See gitrepository-layout.txt.
--
Duy
next prev parent reply other threads:[~2010-11-03 0:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 17:22 rebase not honoring core.worktree pointing elsewhere Paul Drews
2010-11-01 17:38 ` Sverre Rabbelier
2010-11-02 0:11 ` Nguyen Thai Ngoc Duy
2010-11-02 1:21 ` Junio C Hamano
2010-11-02 16:26 ` Paul Drews
2010-11-03 0:13 ` Nguyen Thai Ngoc Duy [this message]
2010-11-03 15:41 ` Paul Drews
2010-11-03 15:52 ` Nguyen Thai Ngoc Duy
2010-11-03 16:13 ` Jonathan Nieder
2010-11-04 14:20 ` Nguyen Thai Ngoc Duy
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='AANLkTi=T5kHfgNOpOtCDCoq7epEgwUrVayaUCbf35dSU@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=paul.drews@intel.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.