Your message dated Sun, 16 Dec 2018 13:50:47 -0800
with message-id <[email protected]>
and subject line Re: git-submodule issues with detached work trees
has caused the Debian Bug report #707083,
regarding "git submodule add" errors out with "working tree already exists" if
GIT_WORK_TREE is set
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
707083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707083
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git
Version: 1:1.7.10.4-1+wheezy1
Severity: important
Tags: patch
As described in [1], git-submodule is not correctly working with detached work
trees.
git-submodule fails to add submodules, as it is confused by GIT_DIR and
GIT_WORK_TREE environment variables when it tries to work in the submodule.
Please see the upstream fix [2]:
be8779f git-submodule: work with GIT_DIR/GIT_WORK_TREE
Could we think about integrating it for the git version used in wheezy?
[1]
http://git.661346.n2.nabble.com/PATCH-Solve-git-submodule-issues-with-detached-work-trees-tt7563377.html
[2] https://github.com/git/git/commit/be8779f7ac9a3be9aa783df008d59082f4054f67
Thanks,
--
William
--- End Message ---
--- Begin Message ---
Hi again,
In May, 2013, William Dauchy wrote:
> On Tue, May 7, 2013 at 11:24 PM, Jonathan Nieder <[email protected]> wrote:
>> Thanks for writing. It does seem low-risk. Can you say a little more
>> about your workflow? Do you work on a wheezy system or squeeze +
>> squeeze-backports? Would you be willing to use a package from
>> wheezy-backports if available? Where do GIT_DIR and GIT_WORK_TREE get
>> set: are they part of scripts that you use, something you set by hand,
>> or set some other way?
>
> We are using a wheezy system. In fact we have already applied the
> patch I mentioned to fix our service but an upstream package is always
> more suitable.
> A wheezy-backports would be a possible solution if available but since
> the fix seems to me low-risk as well I thought it could be a nice
> solution to propose the fix as a wheezy update.
> GIT_WORK_TREE and GIT_DIR are indeed set by our script (env variable)
> but you have default values as well.
Thanks again for this proposal. I'm marking it closed since it's
fixed in stable and oldstable but I am still quite grateful for the
thoughtful replies back then.
Upstream, submodule support is being handled more and more in-process
in C code. Hopefully it will make these sorts of issues less
frequent.
--- End Message ---
