Jonathan Nieder [off-list ref] writes:
I am guessing
that putting all user git configuration in one directory is part of
the goal, and separating temporary files like ~/.fontconfig/*.cache*
from configuration files like ~/.mutt/muttrc is another part.
That's another good thing with XDG (~/.config Vs ~/.cache/ for example),
but I don't think Git would have anything user-wide that would not be
configuration.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Matthieu Moy wrote:
That's another good thing with XDG (~/.config Vs ~/.cache/ for example),
but I don't think Git would have anything user-wide that would not be
configuration.
Of course, but your home directory that you read with "ls -A" does.
Putting configuration in ~/.config makes it easier to find amid all
that noise.
That said, as Junio wrote before[1]:
It is not _too_ bad to treat ~/.gitconfig specially and support reading
from ~/.$SOMEGITTTYNAME/{excludes,attributes} files.
That's what vim does --- its main configuration file is ~/.vimrc, and
there are also some supporting files in ~/.config/vim/.
Wouldn't that be a good place to start?
Jonathan
[1] http://thread.gmane.org/gmane.comp.version-control.git/133343/focus=135921
Jonathan Nieder wrote:
as Junio wrote before[1]:
quoted
It is not _too_ bad to treat ~/.gitconfig specially and support reading
from ~/.$SOMEGITTTYNAME/{excludes,attributes} files.
That's what vim does --- its main configuration file is ~/.vimrc, and
there are also some supporting files in ~/.config/vim/.
Wouldn't that be a good place to start?
Correction: I meant "also some supporting files in ~/.vim/".
Sorry for the noise.
Jonathan