From: Sergio <sergio.callegari@gmail.com>
To: git@vger.kernel.org
Subject: Re: [RFC] GIT_WORK_TREE
Date: Sun, 3 Jun 2007 21:34:04 +0000 (UTC) [thread overview]
Message-ID: <loom.20070603T232437-414@post.gmane.org> (raw)
In-Reply-To: 20070603193203.GA24781@moooo.ath.cx
Matthias Lederhofer <matled <at> gmx.net> writes:
> What I haven't thought through is if it could make sense to honor the
> GIT_WORK_TREE/core.worktree setting when such a .git-repo file is used
> or just use the directory containing the file as work tree.
I would do the first... for the following reason...
Suppose that by accident you move the working tree and you cd to some
point in the moved WT...
You issue a git command...
By climbing up the directory hierarchy, git gets to the .git-repo file
so now it knows where the repo is...
But running a command and following the core.worktree config it might
put output in the wrong output dir...
But actually I also see problems the other way round...
Suppose you have project A containing a dir B that is under its own git
tracking...
Also suppose that both A and B have repos separated from WT.
If for some reason WT of B misses its .git-repo, then there is trouble
on the way: when issuing a command in B, by climbing up git would find
the .git-repo of A, thinking that it is the git-repo of B...
A weird case, though.
Sergio
next prev parent reply other threads:[~2007-06-03 21:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 14:44 [RFC] GIT_WORK_TREE Matthias Lederhofer
2007-06-03 14:46 ` [PATCH 1/7] rev-parse: document --is-inside-git-dir Matthias Lederhofer
2007-06-03 14:46 ` [PATCH 2/7] rev-parse: introduce --is-bare-repository Matthias Lederhofer
2007-06-03 14:47 ` [PATCH 3/7] test git rev-parse Matthias Lederhofer
2007-06-06 7:01 ` [PATCH 3/7 (amend)] " Matthias Lederhofer
2007-06-03 14:47 ` [PATCH 4/7] introduce GIT_WORK_TREE to specify the work tree Matthias Lederhofer
2007-06-05 7:52 ` Junio C Hamano
2007-06-05 16:49 ` [PATCH] filter-branch: always export GIT_DIR if it is set Matthias Lederhofer
2007-06-05 17:27 ` Johannes Schindelin
2007-06-05 20:39 ` Junio C Hamano
2007-06-06 7:16 ` [PATCH (amend)] " Matthias Lederhofer
2007-06-06 7:10 ` [PATCH 4/7 (amend)] introduce GIT_WORK_TREE to specify the work tree Matthias Lederhofer
2007-06-03 14:48 ` [RFC] GIT_WORK_TREE Matthias Lederhofer
2007-06-03 14:51 ` Matthias Lederhofer
2007-06-03 14:48 ` [PATCH 6/7] extend rev-parse test for --is-inside-work-tree Matthias Lederhofer
2007-06-06 7:13 ` [PATCH 6/7 (amend)] " Matthias Lederhofer
2007-06-03 14:49 ` [PATCH 7/7] test GIT_WORK_TREE Matthias Lederhofer
2007-06-06 7:14 ` [PATCH 7/7 (amend)] " Matthias Lederhofer
2007-06-03 16:02 ` [RFC] GIT_WORK_TREE Sergio
2007-06-03 19:32 ` Matthias Lederhofer
2007-06-03 21:34 ` Sergio [this message]
2007-06-06 21:29 ` [PATCH] setup_git_directory: fix segfault if repository is found in cwd Matthias Lederhofer
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=loom.20070603T232437-414@post.gmane.org \
--to=sergio.callegari@gmail.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).