Yeah, I was not thinking of the potential circular dependencies, but to my mind with correct and explicit resolution order we can deal with it. What is next steps for working with this?
I don't know about development in git, and its code database either. Can you guide me with links? Also, I see some good stuff to do in mailing list, but don't know what is first step. :( 2018-03-18 16:08 GMT+03:00 Ævar Arnfjörð Bjarmason <ava...@gmail.com>: > > On Tue, Mar 13 2018, Ivan Chernov jotted: > > > Hello, fellows. > > > > Git config supports an includeIf statement for conditional > > including https://git-scm.com/docs/git-config#_includes, but in > conditional > > statement included only gitdir. Can we add condition for origin > remote-url? > > Or for remote urls with used names, something like - > > remote:origin:*github.com*. > > Example usage for this feature currently can be done with init hook on > > cloning repo, but can be applied to already cloned one: > > https://github.com/DrVanScott/git-clone-init > > > > P.S. if this proposal need to be sended somewhere else, please, respond > in > > answer. > > This is a very interesting suggestion. I wonder if this wouldn't create > some bizarro circular dependency in the config mechanism though, since > we need to go and figure out the config in order to resolve this. We > read the per-repo config after we read the ~/.gitconfig, where you'd > presumably want to set this. > > I made an indirect mention of this in this E-Mail of mine: > https://public-inbox.org/git/87in9ucsbb....@evledraar.gmail.com/ > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
