On Mon, May 09, 2016 at 10:32:50AM -0700, Stefan Beller wrote:
> >> Here is what I imagine
> >> When B mirrors from A, B sets up this special ref for its repository,
> >> e.g. refs/meta/submodule-B and have a symbolic ref pointing at that.
> >> (e.g. SUBMODULE_CONFIG pointing at refs/meta/submodule
On Mon, May 09, 2016 at 09:19:44AM -0700, Junio C Hamano wrote:
> Heiko Voigt writes:
>
> >> > - When upstream adds a new submodule, I have to do the same manual
> >> > work to change the options for that new submodule.
> >>
> >> Because a new module is not automatically "init"ed by default?
>
>> Here is what I imagine
>> When B mirrors from A, B sets up this special ref for its repository,
>> e.g. refs/meta/submodule-B and have a symbolic ref pointing at that.
>> (e.g. SUBMODULE_CONFIG pointing at refs/meta/submodule-B,
>> which has a worktree which contains a .gitmodules files which
>>
Heiko Voigt writes:
>> > - When upstream adds a new submodule, I have to do the same manual
>> > work to change the options for that new submodule.
>>
>> Because a new module is not automatically "init"ed by default?
>>
>> Isn't "config only" vs "config with gitmodules fallback" orthogonal
>>
Hi,
On Wed, May 04, 2016 at 02:13:47PM -0700, Junio C Hamano wrote:
> Jonathan Nieder writes:
>
> > This design is somewhat problematic for a few reasons:
> >
> > - When I want to stop paying attention to a particular submodule and
> > start paying attention to it again later, all my local set
Hi,
On Wed, May 04, 2016 at 01:50:24PM -0700, Stefan Beller wrote:
> On Wed, May 4, 2016 at 8:01 AM, Heiko Voigt wrote:
> > On Tue, May 03, 2016 at 05:59:58PM -0700, Stefan Beller wrote:
> >> On Tue, May 3, 2016 at 4:56 PM, Jonathan Nieder wrote:
> >> > Stefan Beller wrote:
> >> >
> >> >> This i
Jonathan Nieder writes:
> This design is somewhat problematic for a few reasons:
>
> - When I want to stop paying attention to a particular submodule and
> start paying attention to it again later, all my local settings are
> gone.
True; "[submodule "foo"] enabled = no" may also be a way to
On Wed, May 4, 2016 at 8:01 AM, Heiko Voigt wrote:
> On Tue, May 03, 2016 at 05:59:58PM -0700, Stefan Beller wrote:
>> On Tue, May 3, 2016 at 4:56 PM, Jonathan Nieder wrote:
>> > Stefan Beller wrote:
>> >
>> >> This is similar to the gitignore document, but doesn't mirror
>> >> the current situat
Stefan Beller writes:
> This is similar to the gitignore document, but doesn't mirror
> the current situation. It is rather meant to start a discussion for
> the right approach for mirroring repositories with submodules.
>
> Signed-off-by: Stefan Beller
> ---
>
> Jonathan, is this something you
On Tue, May 03, 2016 at 05:59:58PM -0700, Stefan Beller wrote:
> On Tue, May 3, 2016 at 4:56 PM, Jonathan Nieder wrote:
> > Stefan Beller wrote:
> >
> >> This is similar to the gitignore document, but doesn't mirror
> >> the current situation. It is rather meant to start a discussion for
> >> the
On Tue, May 3, 2016 at 4:56 PM, Jonathan Nieder wrote:
> Stefan Beller wrote:
>
>> This is similar to the gitignore document, but doesn't mirror
>> the current situation. It is rather meant to start a discussion for
>> the right approach for mirroring repositories with submodules.
>
> Ooh.
Thanks
Stefan Beller wrote:
> This is similar to the gitignore document, but doesn't mirror
> the current situation. It is rather meant to start a discussion for
> the right approach for mirroring repositories with submodules.
Ooh.
[...]
> --- a/Documentation/git-submodule.txt
> +++ b/Documentation/git
12 matches
Mail list logo
