From: martin f krafft <madduck@madduck.net>
To: git discussion list <git@vger.kernel.org>
Subject: inconsistent detached worktree handling: several bugs
Date: Mon, 5 May 2008 17:06:43 +0100 [thread overview]
Message-ID: <20080505160643.GA28318@lapse.madduck.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 3791 bytes --]
I am playing around with detached worktrees and have identified
a number of bugs in the path handling. Specifically, it seems that
while git-status and git-add/git-rm are consistent with respect to
each other, they expose different behaviour in different scenarios.
git-diff, on the other hand, seems broken with respect to worktree
handling.
Let me run you through what I did, bugs are
identified with ###BUG. Output is prefixed with #, which should make
it easier to cut-n-paste to reproduce
Note how $GIT_DIR is set for the first part of this exercise:
mkdir worktree
GIT_DIR=repo.git; export GIT_DIR
git --bare init
# Initialized empty Git repository in repo.git/
git config core.bare false
git config core.worktree ../worktree
echo This is just a file called foo > worktree/foo
git add worktree/foo
# fatal: pathspec 'worktree/foo' did not match any files
###BUG: git should be able to factor out the common path prefix
ls foo
# ls: cannot access foo: No such file or directory
git add foo # very confusing, but works
git commit -m'initial checkin'
# Created initial commit 2f2cdf3: initial checkin
# 1 files changed, 1 insertions(+), 0 deletions(-)
# create mode 100644 foo
git status
## On branch master
# nothing to commit (working directory clean)
git diff
# diff --git a/foo b/foo
# deleted file mode 100644
# index 27b451e..0000000
# --- a/foo
# +++ /dev/null
# @@ -1 +0,0 @@
# -This is just a file called foo
###BUG: git-diff doesn't seem to honour worktree and thinks the file
###was deleted
git diff -- worktree/foo
###BUG: no output, even though path was given
echo Another line >> worktree/foo
git status
# # On branch master
# # Changed but not updated:
# # (use "git add <file>..." to update what will be committed)
# #
# # modified: foo
# #
# no changes added to commit (use "git add" and/or "git commit -a")
git diff -- worktree/foo
###BUG: no output, even though path was given
git add foo
# diff --git a/foo b/foo
# deleted file mode 100644
# index 76404d8..0000000
# --- a/foo
# +++ /dev/null
# @@ -1,2 +0,0 @@
# -This is just a file called foo
# -Another line
git diff --cached
# diff --git a/foo b/foo
# index 27b451e..76404d8 100644
# --- a/foo
# +++ b/foo
# @@ -1 +1,2 @@
# This is just a file called foo
# +Another line
-----------
If worktree is actually an ancestor of the Git repository *and* we
chdir() into the repository, whether GIT_DIR is set or not, things
look different again:
mv ../worktree/* ..
rmdir ../worktree
git config core.worktree ..
git status
# # On branch master
# # Changed but not updated:
# # (use "git add <file>..." to update what will be committed)
# #
# # modified: ../foo
# #
# # Untracked files:
# # (use "git add <file>..." to include in what will be committed)
# #
# # ./
# no changes added to commit (use "git add" and/or "git commit -a")
git diff
# diff --git a/foo b/foo
# deleted file mode 100644
# index 76404d8..0000000
# --- a/foo
# +++ /dev/null
# @@ -1,2 +0,0 @@
# -This is just a file called foo
# -Another line
###BUG: again, git-diff can't find the local file
git add foo
# fatal: pathspec 'repo.git/foo' did not match any files
###BUG: inconsistent with above behaviour, but consistent with
###git-status output
git add ../foo
git commit -m'another linee'
# Created commit d016799: another linee
# 1 files changed, 1 insertions(+), 0 deletions(-)
--
martin | http://madduck.net/ | http://two.sentenc.es/
"i might disagree with what you have to say,
but I'll defend to the death your right to say it."
-- voltaire
spamtraps: madduck.bogus@madduck.net
[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-05-05 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 16:06 martin f krafft [this message]
2008-05-07 8:15 ` inconsistent detached worktree handling: several bugs Santi Béjar
2008-05-07 18:06 ` martin f krafft
2008-05-07 19:20 ` Santi Béjar
2008-05-07 19:32 ` martin f krafft
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=20080505160643.GA28318@lapse.madduck.net \
--to=madduck@madduck.net \
--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).