On Thu, Apr 21, 2016 at 10:48 AM, Stefan Beller wrote:
> On Thu, Apr 21, 2016 at 10:45 AM, Junio C Hamano wrote:
>> Stefan Beller writes:
>>
>>> In case of non bare:
>>>
>>> Get the repo and all its submodules from the specified remote.
>>> (As the submodule is right there, that's the be
On Thu, Apr 21, 2016 at 10:45 AM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> In case of non bare:
>>
>> Get the repo and all its submodules from the specified remote.
>> (As the submodule is right there, that's the best guess to get it from,
>> no need to get it from somewhere
Stefan Beller writes:
> In case of non bare:
>
> Get the repo and all its submodules from the specified remote.
> (As the submodule is right there, that's the best guess to get it from,
> no need to get it from somewhere else. The submodule at the remote
> is the closest match you
On Wed, Apr 20, 2016 at 8:14 PM, Yaroslav Halchenko wrote:
> NB Thank you for the lively discussion!
>
> On Wed, 20 Apr 2016, Stefan Beller wrote:
>
>> >> So currently the protocol doesn't allow to even specify the submodules
>> >> directories.
>
>> > Depends on what you exactly mean by "the proto
NB Thank you for the lively discussion!
On Wed, 20 Apr 2016, Stefan Beller wrote:
> >> So currently the protocol doesn't allow to even specify the submodules
> >> directories.
> > Depends on what you exactly mean by "the protocol", but the
> > networking protocol is about accessing a single repo
On Wed, Apr 20, 2016 at 2:27 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>>> I may be missing the subtleties, but if you are serving others from
>>> a non-bare repository with submodules, I do not think you would want
>>> to expose the in-tree version of the submodule in the first place.
Stefan Beller writes:
>> I may be missing the subtleties, but if you are serving others from
>> a non-bare repository with submodules, I do not think you would want
>> to expose the in-tree version of the submodule in the first place.
>
> Well I would imagine that is the exact point.
> If I was n
On Wed, Apr 20, 2016 at 12:51 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>>> 1. After cloning
>>>
>>> git clone http://localhost:8080/.git
>>>
>>>I cannot 'submodule update' the sub1 in the clone since its url after
>>>'submodule init' would be http://localhost:8080/.git/sub
Stefan Beller writes:
>> 1. After cloning
>>
>> git clone http://localhost:8080/.git
>>
>>I cannot 'submodule update' the sub1 in the clone since its url after
>>'submodule init' would be http://localhost:8080/.git/sub1 . If I
>> manually fix
>>it up -- it seems to proceed norm
On Wed, 20 Apr 2016, Stefan Beller wrote:
> > I do realize that the situation is quite uncommon, partially I guess due
> > to git submodules mechanism flexibility and power on one hand and
> > under-use (imho) on the other, which leads to discovery of regressions
> > [e.g. 1] and corner cases as m
On Wed, Apr 20, 2016 at 8:22 AM, Yaroslav Halchenko wrote:
> Dear Git Folks,
>
> I do realize that the situation is quite uncommon, partially I guess due
> to git submodules mechanism flexibility and power on one hand and
> under-use (imho) on the other, which leads to discovery of regressions
> [
Dear Git Folks,
I do realize that the situation is quite uncommon, partially I guess due
to git submodules mechanism flexibility and power on one hand and
under-use (imho) on the other, which leads to discovery of regressions
[e.g. 1] and corner cases as mine.
[1] http://thread.gmane.org/gmane.co
12 matches
Mail list logo
