Re: [PATCH v2] Let core.excludesfile default to ~/.gitexcludes.
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Dec 30, 2009, 19:49 UTC
- Message-ID
- <7vk4w4z1h6.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <vpqhbr8ttwv.fsf@bauges.imag.fr>
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
Show 8 quoted lines
> Nanako Shiraishi <nanako3@lavabit.com> writes: > >> 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.