From: Geoffrey Irving <irving@naml.us>
To: "Santi Béjar" <santi@agolina.net>
Cc: git@vger.kernel.org, Lars Hjemli <hjemli@gmail.com>
Subject: Re: bug with .git file and aliases
Date: Mon, 20 Jul 2009 11:25:33 -0400 [thread overview]
Message-ID: <7f9d599f0907200825j69ee3c9cj4aef26796c3917d6@mail.gmail.com> (raw)
In-Reply-To: <adf1fd3d0907200818l429e701ds6a42ec49f02d5ba9@mail.gmail.com>
On Mon, Jul 20, 2009 at 11:18 AM, Santi Béjar<santi@agolina.net> wrote:
> 2009/7/20 Geoffrey Irving <irving@naml.us>:
>> On Mon, Jul 20, 2009 at 10:04 AM, Santi Béjar<santi@agolina.net> wrote:
>>> 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`
>>
>> Nope, that has no effect.
>
> Here it has the desired effect. From where did you run the above
> command? What is the output of:
>
> git config core.workdir
top:a% git config core.workdir
/Users/irving/tmp/tmp/repo
top:a% git st
# On branch master
# Changed but not updated:
# (use "git add/rm <file>..." to update what will be committed)
# (use "git checkout -- <file>..." to discard changes in working directory)
#
# deleted: a/b
#
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# b
It doesn't matter, though, since setting workdir should not be necessary.
Geoffrey
next prev parent reply other threads:[~2009-07-20 15:26 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
2009-07-20 14:27 ` Geoffrey Irving
2009-07-20 15:18 ` Santi Béjar
2009-07-20 15:25 ` Geoffrey Irving [this message]
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=7f9d599f0907200825j69ee3c9cj4aef26796c3917d6@mail.gmail.com \
--to=irving@naml.us \
--cc=git@vger.kernel.org \
--cc=hjemli@gmail.com \
--cc=santi@agolina.net \
/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).