For instance I want to put some git extensions into my project git
repository. The documentation states that the path must be accessible
through git --ext-path. This can be altered either globally or
per-repository basis in .config. But this file seems to be unversioned. If
we in future will have a need to move/rename our extensions folder -
everybody who contributes to project will have to manually alter .config
file in his repository copy.
вторник, 3 июня 2014 г., 14:24:43 UTC+3 пользователь Pierre-François
> I want to extend git commands set on per-repository basis and therefore I
>> need to have VERSIONED sort of .config file
> You can use the repository's .git/config file to set repo-specific
> configuration, but why would you want it to be versioned in the project
> itself? It'd force anybody who can clone the repo to have the same config
> I guess that the closer you could get to this would be to version a, say,
> git.config file in the project root and then replace the repo's
> .git/config file with a symlink to it. But keep in mind that it'll still
> require whoever can clone the repo to decide to do so, you won't be able to
> force them -- and doing so will prevent them from having their own
> per-repository config file.
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
For more options, visit https://groups.google.com/d/optout.