git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yann Dirson <ydirson@free.fr>
To: GIT list <git@vger.kernel.org>
Subject: [BUG] git-gui regression in 2.0rcX within submodule
Date: Tue, 13 May 2014 01:45:19 +0200	[thread overview]
Message-ID: <20140512234518.GB5529@home.lan> (raw)

In 2.0rc2, git-gui is unable to work inside submodules, where 1.9.2
did not show such a problem:


yann@home:~$ cd /tmp/
yann@home:tmp$ mkdir foo
yann@home:tmp$ cd foo/
yann@home:foo$ git init
Initialized empty Git repository in /tmp/foo/.git/
yann@home:foo (master)$ git submodule add git://git.debian.org/git/collab-maint/tulip.git debian
Cloning into 'debian'...
remote: Counting objects: 317, done.
remote: Compressing objects: 100% (199/199), done.
remote: Total 317 (delta 184), reused 166 (delta 95)
Receiving objects: 100% (317/317), 73.81 KiB | 0 bytes/s, done.
Resolving deltas: 100% (184/184), done.
Checking connectivity... done.
yann@home:foo (master)$ git status 
On branch master

Initial commit

Changes to be committed:
  (use "git rm --cached <file>..." to unstage)

        new file:   .gitmodules
        new file:   debian

yann@home:foo (master)$ (cd debian/ && git gui)
[errors out after showing the following error dialog]

| No working directory ../../../debian:
| 
| couldn't change working directory
| to "../../../debian": no such file or
| directory


strace shows the failing chdir call is from git-gui itself, after
getcwd() told him that it is in the dir that is indeed the workdir
already.

             reply	other threads:[~2014-05-12 23:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12 23:45 Yann Dirson [this message]
2014-05-13  8:30 ` [BUG] git-gui regression in 2.0rcX within submodule Chris Packham
2014-05-13 21:14   ` Jens Lehmann

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=20140512234518.GB5529@home.lan \
    --to=ydirson@free.fr \
    --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).