Jeff King p...@peff.net writes:
Yeah, I'm not planning to work on this, but I'd be happy to review
patches if somebody else wants to.
I am not planning to work on this, and honestly speaking I would not
be very happy to see any patch in this area.
--
To unsubscribe from this list: send the
Jeff King p...@peff.net writes:
I'd rather not invent a new language. It will either not be featureful
enough, or will end up bloated. Or both. How about something like:
[include]
exec =
case \$GIT_DIR\ in)
*/dev/*) cat ~/.config/git/dev-config ;;
On Fri, Mar 22, 2013 at 05:06:28PM -0700, Jonathan Nieder wrote:
I'd rather not invent a new language. It will either not be featureful
enough, or will end up bloated. Or both. How about something like:
[include]
exec =
case \$GIT_DIR\ in)
*/dev/*) cat
On Sat, Mar 23, 2013 at 07:15:42AM +0100, Thomas Rast wrote:
It involves a shell invocation, but it's not like we parse config in a
tight loop. Bonus points if git provides the name of the current config
file, so exec can use relative paths like:
We do, however, parse config more than
It'd be cool if I were able to override config settings at every
nested directory.
For example, I have my ~/.gitconfig that has one email address in it,
but I also have multiple repos inside ~/dev which I want to use a
different email address for. The only way to do that now is to edit
all of
Hi Josh,
Josh Sharpe wrote:
For example, I have my ~/.gitconfig that has one email address in it,
but I also have multiple repos inside ~/dev which I want to use a
different email address for. The only way to do that now is to edit
all of these: ~/dev/*/.git/conf -- and there are lots of
On Fri, Mar 22, 2013 at 11:22:11AM -0700, Jonathan Nieder wrote:
* Maintaining configuration per repository to record a rather simple
is more complicated than ideal. It would be easier to understand
the configuration if ~/.gitconfig could spell out the rule
explicitly:
Jeff King wrote:
On Fri, Mar 22, 2013 at 11:22:11AM -0700, Jonathan Nieder wrote:
It would be easier to understand
the configuration if ~/.gitconfig could spell out the rule
explicitly:
[...]
It sounds hard to do right, especially considering use
8 matches
Mail list logo