Re: [RFC 00/10] Make .the gitmodules file path configurable

On Mon, 23 Apr 2018 10:47:09 -0700 Jonathan Nieder wrote: > Hi, > Hi Jonathan, thank you for your comment. > Antonio Ospite wrote: > > > vcsh[1] uses bare git repositories and detached work-trees to manage > > *distinct* sets of configuration files directly into $HOME. >

Re: [RFC 00/10] Make .the gitmodules file path configurable

Hi, Antonio Ospite wrote: > vcsh[1] uses bare git repositories and detached work-trees to manage > *distinct* sets of configuration files directly into $HOME. Cool! I like the tooling you're creating for this, though keep in mind that Git has some weaknesses as a tool for deployment. In

Re: [RFC 00/10] Make .the gitmodules file path configurable

Hi Antonio, > I acknowledge that the two mechanisms are different, in particular > because git *writes* the gitmodules file itself. > > I am not opposed to change the name, something like > 'core.submodulesConfigFile' might highlight that the syntax of the file > is the one of git config, but I

Re: [RFC 00/10] Make .the gitmodules file path configurable

On Thu, 12 Apr 2018 16:36:32 -0700 Stefan Beller wrote: > Hi Antonio, > Hi Stefan, > On Thu, Apr 12, 2018 at 3:20 PM, Antonio Ospite wrote: > > Hi, > > > > vcsh[1] uses bare git repositories and detached work-trees to manage > > *distinct* sets of

Re: [RFC 00/10] Make .the gitmodules file path configurable

On Fri, 13 Apr 2018 00:20:37 +0200 Antonio Ospite wrote: [...] > Antonio Ospite (10): > submodule: add 'core.submodulesFile' to override the '.gitmodules' > path > submodule: fix getting custom gitmodule file in fetch command > submodule: use the 'submodules_file' variable

Re: [RFC 00/10] Make .the gitmodules file path configurable

Hi Antonio, On Thu, Apr 12, 2018 at 3:20 PM, Antonio Ospite wrote: > Hi, > > vcsh[1] uses bare git repositories and detached work-trees to manage > *distinct* sets of configuration files directly into $HOME. > > In general, submodules have worked perfectly fine with detached >

[RFC 00/10] Make .the gitmodules file path configurable

Hi, vcsh[1] uses bare git repositories and detached work-trees to manage *distinct* sets of configuration files directly into $HOME. In general, submodules have worked perfectly fine with detached work-trees for some time[2,3,4]. However when multiple repositories take turns using the same