Re: [RFC-PATCHv2] submodules: add a background story

2017-02-14 Thread Junio C Hamano
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

Re: [RFC-PATCHv2] submodules: add a background story

2017-02-14 Thread Junio C Hamano
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

Re: [RFC-PATCHv2] submodules: add a background story

2017-02-14 Thread Stefan Beller
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

Re: [RFC-PATCHv2] submodules: add a background story

2017-02-14 Thread Junio C Hamano
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 =

Re: [RFC-PATCHv2] submodules: add a background story

2017-02-14 Thread Stefan Beller
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 = . >> ... >> >>

Re: [RFC-PATCHv2] submodules: add a background story

2017-02-14 Thread Junio C Hamano
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

Re: [RFC-PATCHv2] submodules: add a background story

2017-02-14 Thread Stefan Beller
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

Re: [RFC-PATCHv2] submodules: add a background story

2017-02-13 Thread Brandon Williams
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 > +

Re: [RFC-PATCHv2] submodules: add a background story

2017-02-09 Thread Junio C Hamano
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

[RFC-PATCHv2] submodules: add a background story

2017-02-08 Thread Stefan Beller
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