On Thu, Jan 21, 2016 at 10:56 PM, Stefan Beller wrote:
>>> [submodule "gcc"]
>>> path = gcc
>>> url = git://...
>>> groups = default
>>> groups = devel
>>
>> On the quick I was unable to find the rationale why entries are now stored
>> as
Stefan Beller writes:
> I think having both is bad as it may contradict each other?
> What is supposed to happen here:
>
> [submodule "frotz"]
> group = default
>
> [submoduleGroup "default"]
> member = !:frotz
What is supposed to happen is that
On Thu, Jan 21, 2016 at 1:17 PM, Sebastian Schuberth
wrote:
> On 20.01.2016 04:34, Stefan Beller wrote:
>
>> So you could have a .gitmodules file such as:
>>
>> [submodule "gcc"]
>> path = gcc
>> url = git://...
>> groups = default
>>
On Thu, Jan 21, 2016 at 2:18 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> Instead of having a submodule -> set assignment, we could do it the
>> other way round:
>>
>> [submodule "gcc"]
>> ...
>>
>> [submodule-set "default"]
>>
On 20.01.2016 04:34, Stefan Beller wrote:
> So you could have a .gitmodules file such as:
>
> [submodule "gcc"]
> path = gcc
> url = git://...
> groups = default
> groups = devel
On the quick I was unable to find the rationale why entries are now stored as
Stefan Beller writes:
> Instead of having a submodule -> set assignment, we could do it the
> other way round:
>
> [submodule "gcc"]
> ...
>
> [submodule-set "default"]
> submodule = gcc
> submodule = foo
> submodule = by/path/*
>
>
Junio C Hamano writes:
> I suspect that we will end up needing to support both styles. The
> latter style is easier when you want to express a larger set as a
> collection of groups, e.g.
> ...
> might be a way to say "the default group includes everything in the
>
7 matches
Mail list logo