Brandon Williams writes:
>> +The method by which a submodule is updated by 'git submodule update',
>> +which is the only affected command, others such as
>> +'git checkout --recurse-submodules' are unaffected. It exists for
>> +historical reasons, when 'git
Stefan Beller wrote:
> By as-is I refer to origin/pu.
Ah, okay. I'm not in that habit because pu frequently loses topics
--- it's mostly useful as a tool to (1) distribute topic branches and
(2) check whether they are compatible with each other.
[...]
> On Mon, Sep 25, 2017 at 3:22 PM,
On Mon, Sep 25, 2017 at 3:22 PM, Jonathan Nieder wrote:
> Stefan Beller wrote:
>> On Mon, Sep 25, 2017 at 12:17 PM, Brandon Williams wrote:
>>> On 09/25, Stefan Beller wrote:
>
Have one place to explain the effects of setting submodule..update
Stefan Beller wrote:
> On Mon, Sep 25, 2017 at 12:17 PM, Brandon Williams wrote:
>> On 09/25, Stefan Beller wrote:
>>> Have one place to explain the effects of setting submodule..update
>>> instead of two.
>>>
>>> Signed-off-by: Stefan Beller
>>> ---
>
On Mon, Sep 25, 2017 at 12:17 PM, Brandon Williams wrote:
> On 09/25, Stefan Beller wrote:
>> Have one place to explain the effects of setting submodule..update
>> instead of two.
>>
>> Signed-off-by: Stefan Beller
>> ---
>> >> I disagree. Actually, I
On 09/25, Stefan Beller wrote:
> Have one place to explain the effects of setting submodule..update
> instead of two.
>
> Signed-off-by: Stefan Beller
> ---
> >> I disagree. Actually, I think the git-config(1) blurb could just
> >> point here, and that the text here ought to
Have one place to explain the effects of setting submodule..update
instead of two.
Signed-off-by: Stefan Beller
---
>> I disagree. Actually, I think the git-config(1) blurb could just
>> point here, and that the text here ought to be clear about what
>> commands it affects
7 matches
Mail list logo