From: "Сергей Шарыбин" <nazgul@school9•perm.ru>
To: git@vger•kernel.org
Subject: Problem with --work-tree
Date: Sun, 17 Aug 2008 03:14:13 +0600 [thread overview]
Message-ID: <48A74325.1040805@school9.perm.ru> (raw)
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?
--
With best regards, Sergey I. Sharybin
next reply other threads:[~2008-08-16 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 21:14 Сергей Шарыбин [this message]
2008-08-17 5:24 ` Problem with --work-tree Nguyen Thai Ngoc Duy
2008-08-18 9:32 ` Michael J Gruber
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=48A74325.1040805@school9.perm.ru \
--to=nazgul@school9$(echo .)perm.ru \
--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