-
Notifications
You must be signed in to change notification settings - Fork 601
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
submodules cause: Failed to chdir(../../../ #54
Comments
When in a submodule, you first need to chdir into the git_dir, and then use the value of "core.worktree" as a relative path. In tig, it moves into the git_dir and then checks that cwd is still availble, thus breaking the relative path. Fixes jonas#54
When in a submodule, you first need to chdir into the git_dir, and then use the value of "core.worktree" as a relative path. In tig, it moves into the git_dir and then checks that cwd is still availble, thus breaking the relative path. Signed-off-by: Jonas Fonseca <fonseca@diku.dk>
Any idea when this will make it into a release? Since I use submodules extensively it is disrupting my workflow. I'll probably just run off of master for now though. |
if you're on osx theres a HEAD build for tig in my homebrew repo, it
|
I plan to make a maintenance release soon. Anyway, the patch has been integrated into master, so will close. |
Hey Jonas. I have the same issue
I have a subdirectory submodule |
@MasseGuillaume can you try with the latest version (tig 1.2) or master? |
Hi @MasseGuillaume, submodules are known to be supported in version 1.1 and master - and broken in 1.0 and 1.2 :( ... I plan to release a 1.2.1 sometime this week. |
When using tig with submodules created with the current version of git the following behavior is observed:
The current version of git creates a config file in the submodule's .git location - whereas in the past it would be a complete .git folder (and tig would happily use that).
The text was updated successfully, but these errors were encountered: