On Thu, 3 May 2018 11:12:27 -0700
Stefan Beller wrote:
> >> There are three different possible solutions that have more value:
> >> (a) The path value is documented as the path from the toplevel of the
> >> superproject to the mount point of the submodule. If 'the' refers
On Thu, May 3, 2018 at 10:47 AM, Jonathan Tan wrote:
> On Wed, 2 May 2018 17:53:54 -0700
> Stefan Beller wrote:
>
>> From: Prathamesh Chavan
>>
>> When running 'git submodule foreach --recursive' from a subdirectory of
>> your
On Wed, 2 May 2018 17:53:54 -0700
Stefan Beller wrote:
> From: Prathamesh Chavan
>
> When running 'git submodule foreach --recursive' from a subdirectory of
> your repository, nested submodules get a bogus value for $path:
I know I said in a previous
On 03/05/18 01:53, Stefan Beller wrote:
> From: Prathamesh Chavan
>
> When running 'git submodule foreach --recursive' from a subdirectory of
> your repository, nested submodules get a bogus value for $path:
> For a submodule 'sub' that contains a nested submodule 'nested',
From: Prathamesh Chavan
When running 'git submodule foreach --recursive' from a subdirectory of
your repository, nested submodules get a bogus value for $path:
For a submodule 'sub' that contains a nested submodule 'nested',
running 'git -C dir submodule foreach echo $path'
5 matches
Mail list logo