On Mon, Mar 18, 2019 at 1:52 PM Duy Nguyen <[email protected]> wrote: > > On Mon, Feb 4, 2019 at 4:17 PM Christian Couder > <[email protected]> wrote:
> > Anyway feel free to comment and suggest improvements on those pages, > > especially the micro-projects and ideas one. Pull requests on > > https://github.com/git/git.github.io/ are very much appreciated. > > I'm not opening a pull request because I'm not sure if it's worthy of > GSoC (probably 2020, not 2019) but anyway the get_config_* discussion > elsewhere reminds me of this. I think it would be nice to have a section with potential ideas along with a big warning saying that the ideas there aren't developed enough as is and need much more work/thinking to be considered proper ideas, but we are still putting them there to not forget about them and in case someone would be interested to develop/research them further. > Currently we have two ways of parsing config files, by a callback that > gives you everything and you do whatever you want, and with configset > where you can just call "get me this config", "get me that one". The > idea is moving most callback-based sites to get_config_ one. > Preferably in a declarative style, like 'struct option[]'. Thanks, I like this idea! Maybe it could be even considered for microprojects, as I think it could be done in many small steps. It would perhaps need to point to en existing commit doing already that to make it clearer and easier though.
