Re: [PATCH v2] Let core.excludesfile default to ~/.gitexcludes.

Nanako Shiraishi [off-list ref] writes:

Junio, could you tell us what happened to this thread?

I'm not Junio, but I can try ...

Setting a default for core.excludesfile implies that changing it later
is hard. In particular, _if_ we chose one day to move from multiple
$HOME/.gitsomething files to $HOME/something-else/multiple-files
($XDG_CONFIG_HOME and $HOME/.gitglobal/{config,excludes,...} have been
suggested, as well as a $GIT_HOME variable), then the transition is
made harder by having a default.

So, while I think having a default is good, chosing the default
shouldn't be taken lightly.

I personally like the idea of a user config _directory_ with multiple
files in it, but I'm not clear on exactly what it should be, how the
transition plan would be, ...

So, I dropped the patch until we get closer to a consensus on what the
default value should be.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

Matthieu Moy [off-list ref] writes:

Nanako Shiraishi [off-list ref] writes:

quoted

Junio, could you tell us what happened to this thread?

I'm not Junio, but I can try ...
...
So, I dropped the patch until we get closer to a consensus on what the
default value should be.

Thanks for status updates.  Should we start trying to reach a consensus on
how to move forward, or is it not your itch?

It is not _too_ bad to treat ~/.gitconfig specially and support reading
from ~/.$SOMEGITTTYNAME/{excludes,attributes} files.  We can also add
support for ~/.$SOMEGITTYNAME/config and try reading from it as well, but
even if we did so I don't think we should stop reading from ~/.gitconfig.

I don't have strong preference myself either way.