From: Michael J Gruber <git@drmicha•warpmail.net>
To: Matthieu Moy <Matthieu.Moy@imag•fr>
Cc: git@vger•kernel.org, gitster@pobox•com
Subject: Re: [PATCH (resend)] Let core.excludesfile default to ~/.gitexcludes.
Date: Thu, 26 Nov 2009 13:00:09 +0100 [thread overview]
Message-ID: <4B0E6DC9.3070105@drmicha.warpmail.net> (raw)
In-Reply-To: <1259231726-5218-1-git-send-email-Matthieu.Moy@imag.fr>
Matthieu Moy venit, vidit, dixit 26.11.2009 11:35:
> Most users will set it to ~/.gitsomething. ~/.gitignore would conflict
> with per-directory ignore file if ~/ is managed by Git, so ~/.gitexcludes
> is a sane default.
I'm sorry to jump in so late, and this may sound like bike-shedding, but
right now we have
.git/info/exclude
.gitignore
and this would add
~/.gitexcludes
That is, three terms, or two, where one comes in two variations
(exclude/exludes). I always wondered why we have two.
The reason for .gitignore is most probably the similarity to
.${othervcs}ignore, and that is a valid reason.
I know we have ~/.gitconfig for the global version of .git/config, and
maybe that was just no good idea either. But I don't even dare
suggesting to rename it ~/.gitglobalconfig.
So, in line at least with our term "global" (per user) config, I would
suggest to use "~/.gitglobalignore" for the global ignore file. Maybe,
eventually, we'll manage to rename .git/info/excludes to .git/info/ignore.
On a somewhat larger scale, a good alternative strategy would be to have
a directory "~/.gitglobal/" in which Git would look for
~/.gitglobal/config and
~/.gitglobal/info/ignore or
~/.gitglobal/ignore
i.e. mirroring the repo structure or at least bundling everything in a
single dir, which would also be a good place for a global svnauthors
file and such, and for other global configuration files we don't think
of right now.
Michael
next prev parent reply other threads:[~2009-11-26 12:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 13:23 [PATCH] let core.excludesfile default to ~/.gitignore Matthieu Moy
2009-11-20 14:30 ` Stefan Naewe
2009-11-20 18:50 ` David Aguilar
2009-11-21 22:00 ` [PATCH v2] Let core.excludesfile default to ~/.gitexcludes Matthieu Moy
2009-11-26 10:35 ` [PATCH (resend)] " Matthieu Moy
2009-11-26 12:00 ` Michael J Gruber [this message]
2009-11-26 12:49 ` Paolo Bonzini
2009-11-26 13:27 ` Michael J Gruber
2009-11-26 13:01 ` Bert Wesarg
2009-11-26 13:39 ` Michael J Gruber
2009-11-26 20:07 ` David Aguilar
2009-11-26 18:18 ` Junio C Hamano
2009-12-30 13:41 ` [PATCH v2] " Nanako Shiraishi
2009-12-30 14:31 ` Matthieu Moy
2009-12-30 19:49 ` Junio C Hamano
2010-01-02 12:05 ` User-wide Git config directory (was Re: [PATCH v2] Let core.excludesfile default to ~/.gitexcludes.) Matthieu Moy
2009-11-20 22:49 ` [PATCH] let core.excludesfile default to ~/.gitignore Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B0E6DC9.3070105@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=Matthieu.Moy@imag$(echo .)fr \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox