From: Michael J Gruber <michaeljgruber+gmane@fastmail•fm>
To: git@vger•kernel.org
Subject: Re: Problem with --work-tree
Date: Mon, 18 Aug 2008 11:32:28 +0200 [thread overview]
Message-ID: <g8bfjc$551$1@ger.gmane.org> (raw)
In-Reply-To: <48A74325.1040805@school9.perm.ru>
Сергей Шарыбин venit, vidit, dixit 16.08.2008 23:14:
> Hi,
>
> I've got the following problem. I've got a GIT repo at
> /home/nazgul/src/test-work-tree and I've got some changed files in this
> repo. I want to see this changes when a `git` runs outside this
> directory. I tried to run `git
> --git-dir=/home/nazgul/src/test-work-tree/.git
> --work-tree=/home/nazgul/src/test-work-tree diff-index --name-status
> HEAD` from my home directory. In such way diff-index tells me that all
> files from my repo has been deleted. I think it is because this command
> does not understand a --work-tree parameter. And I saw the same problem
> with a git diff command (something like that: git
> --git-dir=/home/nazgul/src/test-work-tree/.git
> --work-tree=/home/nazgul/src/test-work-tree diff).
>
> I use git version debian.1.5.6.3.1
>
> Is it my mistake or it is bugs in a GIT?
Working from a path outside the work tree is broken (read: not meeting
the obvious/naive meaning of the --work-tree option and core.worktree
setting) in many places, unfortunately. Some commands work with
--git-dir and the like, but some just don't. I use a shell alias which
cds into the work tree first. This works with everything except for some
stubborn tcl/tk scripts doing their own thing (gui...) in case git-dir
and work-tree are not in the standard places (.git, .).
Michael
prev parent reply other threads:[~2008-08-18 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 21:14 Problem with --work-tree Сергей Шарыбин
2008-08-17 5:24 ` Nguyen Thai Ngoc Duy
2008-08-18 9:32 ` Michael J Gruber [this message]
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='g8bfjc$551$1@ger.gmane.org' \
--to=michaeljgruber+gmane@fastmail$(echo .)fm \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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