git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Yasushi SHOJI <yashi@atmark-techno.com>
Cc: git@vger.kernel.org
Subject: Re: git diff-index with relative git-dir does not work
Date: Tue, 9 Feb 2010 18:58:51 +0700	[thread overview]
Message-ID: <fcaeb9bf1002090358v3d7f69d5ra80c186d30a1304d@mail.gmail.com> (raw)
In-Reply-To: <871vguy8hz.wl@dns1.atmark-techno.com>

On 2/9/10, Yasushi SHOJI <yashi@atmark-techno.com> wrote:
>  ...
>  This is because static variable 'base' in sha1_file_name is already
>  assigned _before_ setup_work_tree() from cmd_diff_index() is
>  called. setup_work_tree() eventually chdir to the given work tree dir,
>  but we use the old base to generate object file path. And that cause
>  open(2) to fail because the object file path and the current dir is
>  not in sync any more.
>
>  So, is it correct to assume that we must call setup_work_tree()
>  _before_ any function which call getter/setter in environment.c?  This
>  including open_sha1_file, in this case.

We must if gitdir is relative to cwd (and will be moved by
setup_work_tree). Or just make gitdir absolute path.

>  Also, would it be a good idea to make all builtin command to
>  _explicitly_ call setup_* functions, so that we can find calling order
>  bug?

If you agree that writing "RUN_SETUP" in git.c is explicit, then all
builtin commands do explictly call setup_*. It's about relative
directories and cwd being moved around.

>  In that case, we must change the setup functions signature to
>  allow marking "not interested" or something.

I'm not sure I get your idea.
-- 
Duy

  reply	other threads:[~2010-02-09 11:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09 11:05 git diff-index with relative git-dir does not work Yasushi SHOJI
2010-02-09 11:58 ` Nguyen Thai Ngoc Duy [this message]
2010-02-09 13:10   ` Yasushi SHOJI
2010-02-11 10:35     ` Nguyen Thai Ngoc Duy

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=fcaeb9bf1002090358v3d7f69d5ra80c186d30a1304d@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=yashi@atmark-techno.com \
    /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).