From: "Santi Béjar" <santi@agolina.net>
To: Geoffrey Irving <irving@naml.us>
Cc: git@vger.kernel.org, Lars Hjemli <hjemli@gmail.com>
Subject: Re: bug with .git file and aliases
Date: Mon, 20 Jul 2009 16:04:52 +0200 [thread overview]
Message-ID: <adf1fd3d0907200704sb097a99h1ab8f118be5854f9@mail.gmail.com> (raw)
In-Reply-To: <7f9d599f0907200654q2e068e6aq3051c122f6596053@mail.gmail.com>
2009/7/20 Geoffrey Irving <irving@naml.us>:
> git 1.6.3.3 has a bug related to .git file support and aliases.
> Specifically, if you make an alias for status and call it from a
> subdirectory, git status chdirs into the true .git dir but then
> chdir's back to the wrong place in order to run the lstats for status.
> The result is that git status thinks all files have disappeared.
>
> Here's a self-contained test script:
>
> #!/bin/bash
> set -x
>
> # make a simple repository
> mkdir repo
> cd repo
> git init
> mkdir a
> echo content > a/b
> git add a/b
> git commit -m "a commit"
>
> # replace the gitdir with a gitfile
> mv .git ../repo.git
> echo gitdir: `pwd`.git > .git
>
> # normal git status works
> cd a
> git status
>
> # an alias for git status fails
> git config alias.st status
> git st
I suspect that the $GIR_DIR and .git file works equally in this
aspect, so you should specify where is the workdir in .git/config with
respect the repository:
git config core.workdir `pwd`
HTH,
Santi
next prev parent reply other threads:[~2009-07-20 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 13:54 bug with .git file and aliases Geoffrey Irving
2009-07-20 14:04 ` Santi Béjar [this message]
2009-07-20 14:27 ` Geoffrey Irving
2009-07-20 15:18 ` Santi Béjar
2009-07-20 15:25 ` Geoffrey Irving
2009-07-20 15:21 ` Jeff King
2009-08-10 20:22 ` Geoffrey Irving
2009-08-10 23:05 ` Johannes Schindelin
2009-08-11 3:37 ` Geoffrey Irving
2009-08-11 8:33 ` Johannes Schindelin
2009-08-11 10:04 ` Michael J Gruber
2009-08-11 10:26 ` Johannes Sixt
2009-08-11 10:37 ` 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=adf1fd3d0907200704sb097a99h1ab8f118be5854f9@mail.gmail.com \
--to=santi@agolina.net \
--cc=git@vger.kernel.org \
--cc=hjemli@gmail.com \
--cc=irving@naml.us \
/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).