Re: Submodule's .git file contains absolute path when created using 'git clone --recursive'
- From
Stefan Beller <sbeller@google.com>
- Date
- May 5, 2016, 19:32 UTC
- Message-ID
- <CAGZ79kYjw6vzf7rf_-bOiMmm0VtAwO03vpk67QP4u2m_N_Mm4g@mail.gmail.com>
- In-Reply-To
- <CAK1enhO-2Ne4XVqRNXz+6Jd7uEEHde8-_xzwWzXh=b01bZhj0g@mail.gmail.com>
On Thu, May 5, 2016 at 12:20 PM, Loet Avramson <loet@forter.com> wrote:
Show 5 quoted lines
> It happened on 2.8.1, also reproducible on 2.8.2. > Haven't had the time to dive deeper into the code but my guess is that > relative_path() returns different results in those 2 cases or maybe > the way git-submodule.sh handles it. >
Then you found a new bug, congratulations. ;) Thanks for reporting.
The shell script uses relative_path() only for displaying paths, not for writing them to the .git file.
it really boils down to different environments "git submodule update --init --recursive" is called from (either manually or from `git clone`).
Apart from that there are no immediate bells ringing, are you doing any weird stuff with the file system (soft/hard links) ?
Thanks, Stefan