Stefan Beller writes:
> I claim that the exposure into .gitmodules combined with
> the extreme similarity to its path is confusing. Maybe this
> can be fixed by a different default name.
I think that this may be worth thinking about it further.
The names are something the
Stefan Beller writes:
>> And then after doing the "git mv" you have pushed the result, which
>> I pulled. Now, how will your "internal mapping" propagate to me?
>
> The "name" inside your superprojects git dir may be different from mine,
> after all the name only serves the
On Tue, Feb 14, 2017 at 2:17 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> On Tue, Feb 14, 2017 at 1:56 PM, Junio C Hamano wrote:
>>> Stefan Beller writes:
>>>
If we were to redesign the .gitmodules
Stefan Beller writes:
> On Tue, Feb 14, 2017 at 1:56 PM, Junio C Hamano wrote:
>> Stefan Beller writes:
>>
>>> If we were to redesign the .gitmodules file, we might have it as
>>>
>>> [submodule "path"]
>>> url =
On Tue, Feb 14, 2017 at 1:56 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> If we were to redesign the .gitmodules file, we might have it as
>>
>> [submodule "path"]
>> url = git://example.org
>> branch = .
>> ...
>>
>>
Stefan Beller writes:
> If we were to redesign the .gitmodules file, we might have it as
>
> [submodule "path"]
> url = git://example.org
> branch = .
> ...
>
> and the "path -> name/UID" mapping would be inside $GIT_DIR.
I am not sure how you are
Sorry for dropping the ball here, I was stressed out a bit.
On Thu, Feb 9, 2017 at 3:32 PM, Junio C Hamano wrote:
>> Do we need
>>
>> * an opinionated way to check for a specific state of a submodule
>> * (submodule helper to be plumbing?)
>> * expose the design
On 02/08, Stefan Beller wrote:
> +STATES
> +--
> +
> +When working with submodules, you can think of them as in a state machine.
> +So each submodule can be in a different state, the following indicators are
> used:
> +
> +* the existence of the setting of 'submodule..url' in the
> +
Stefan Beller writes:
> Just like gitmodules(5), gitattributes(5), gitcredentials(7),
> gitnamespaces(7), gittutorial(7), we'd like to provide some background
> on submodules, which is not specific to the `submodule` command, but
> elaborates on the background and its
Just like gitmodules(5), gitattributes(5), gitcredentials(7),
gitnamespaces(7), gittutorial(7), we'd like to provide some background
on submodules, which is not specific to the `submodule` command, but
elaborates on the background and its intended usage.
Add gitsubmodules(7), that explains the
10 matches
Mail list logo