On Tue, Dec 13, 2016 at 12:09 PM, Stefan Beller wrote:
>
> So I will reroll it with "absorb" fixing some nits pointed out by David?
I got confused there, Davids nits are for this series, the absorb series itself
doesn't seem to have nits.
So I'll just reroll this series on top of the currently
s
On Tue, Dec 13, 2016 at 11:47 AM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> The desired standard for submodules is to have the git dir inside the
>> superprojects git dir (since 501770e, Aug 2011, Move git-dir for
>> submodules), which is why I think an "embedded submodule git dir"
>> i
Stefan Beller writes:
> I guess the latter is the case, so embedding is actually inside
> the working tree and un-embedding is the relocation to the
> superproject.
Another reason why I personally see a .git in each submodule working
tree is "embedded" has nothing to do with Git. It is an analo
Stefan Beller writes:
> The desired standard for submodules is to have the git dir inside the
> superprojects git dir (since 501770e, Aug 2011, Move git-dir for
> submodules), which is why I think an "embedded submodule git dir"
> is inside the superproject already.
Think how you start a new su
On Tue, Dec 13, 2016 at 11:11 AM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>>> I do not think there is no dispute about what embedding means.
>>
>> double negative: You think we have a slight dispute here.
>
> Sorry, I do not think there is any dispute on that.
>
>>> A
>>> submodule whose
On Tue, Dec 13, 2016 at 11:13 AM, Stefan Beller wrote:
> On Tue, Dec 13, 2016 at 11:11 AM, Junio C Hamano wrote:
>> Stefan Beller writes:
>>
I do not think there is no dispute about what embedding means.
>>>
>>> double negative: You think we have a slight dispute here.
>>
>> Sorry, I do not
Stefan Beller writes:
>> I do not think there is no dispute about what embedding means.
>
> double negative: You think we have a slight dispute here.
Sorry, I do not think there is any dispute on that.
>> A
>> submodule whose .git is inside its working tree has its repository
>> embedded.
>>
>
On Tue, Dec 13, 2016 at 10:53 AM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> On Mon, Dec 12, 2016 at 11:28 PM, Junio C Hamano wrote:
>>> Stefan Beller writes:
>>>
The "checkout --recurse-submodules" series got too large to comfortably
send
it out for review, so I had to
Stefan Beller writes:
> On Mon, Dec 12, 2016 at 11:28 PM, Junio C Hamano wrote:
>> Stefan Beller writes:
>>
>>> The "checkout --recurse-submodules" series got too large to comfortably send
>>> it out for review, so I had to break it up into smaller series'; this is the
>>> first subseries, but
On Mon, Dec 12, 2016 at 11:28 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> The "checkout --recurse-submodules" series got too large to comfortably send
>> it out for review, so I had to break it up into smaller series'; this is the
>> first subseries, but it makes sense on its own.
>>
>
Stefan Beller writes:
> The "checkout --recurse-submodules" series got too large to comfortably send
> it out for review, so I had to break it up into smaller series'; this is the
> first subseries, but it makes sense on its own.
>
> This series teaches git-rm to absorb the git directory of a sub
The "checkout --recurse-submodules" series got too large to comfortably send
it out for review, so I had to break it up into smaller series'; this is the
first subseries, but it makes sense on its own.
This series teaches git-rm to absorb the git directory of a submodule instead
of failing and com
12 matches
Mail list logo
