threads / discuss / 33064

Configurable .gitignore filename?

Subject: Configurable .gitignore filename?

## tl;dr

5 messages between Mar 4, 2013 and Mar 5, 2013.

replies: 4people: 3as markdown or json

Jari Pennanen· Mar 4, 2013, 11:58 UTC · lore

If project or directory belongs to more than one GIT_DIR then some of the GIT_DIR's may need a different .gitignore files, it would be useful if one could define it independently, e.g. in GIT_DIR/config:

[core] ignorefilename = .gitalternateignore

Has anyone considered making the .gitignore filename configurable? It could be in a config file or env variable, but either way it would be handy to be configurable. I'm not familiar with git's structure, but if ignoring is only used in git-add then I suppose I could make own git-add script if this is not implemented in core git.

I intend to use GIT as a rsync replica (or Dropbox replica) cause it suits it better than rsync, since GIT doesn't have to check all files each time I sync (and GIT can contain versions / backups, works better on Windows and has a simpler needs for the server), more about why I need this: https://groups.google.com/forum/#!topic/git-users/E-Au9P0A6NA/discussion%5B1-25-false%5D

- Jari

Matthieu Moy· Mar 4, 2013, 13:53 UTC · re: Jari Pennanen · lore

Re: Configurable .gitignore filename?

Jari Pennanen <jari.pennanen@gmail.com> writes:

Show 6 quoted lines

> If project or directory belongs to more than one GIT_DIR then some of
> the GIT_DIR's may need a different .gitignore files, it would be
> useful if one could define it independently, e.g. in GIT_DIR/config:
>
> [core]
> ignorefilename = .gitalternateignore

There is already core.excludesfile, which does not replace the usual .gitignore but comes in addition. The common use is a user-wide ignore file, not a per-directory one.

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

Jari Pennanen· Mar 4, 2013, 15:47 UTC · re: Matthieu Moy · lore

Re: Configurable .gitignore filename?

2013/3/4 Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>:

> There is already core.excludesfile, which does not replace the usual
> .gitignore but comes in addition. The common use is a user-wide ignore
> file, not a per-directory one.

I'm actually aware of that. Problem is the normal .gitignore files must *not* be used in the second GIT_DIR at all, in my case it's for syncing so I need to sync almost all files (including stuff inside .gitignore), though I'd still like to retain some ignore files for second GIT_DIR, e.g. like in rsync the .rsync-filter file.

David Aguilar· Mar 5, 2013, 09:59 UTC · re: Jari Pennanen · lore

Re: Configurable .gitignore filename?

On Mon, Mar 4, 2013 at 7:47 AM, Jari Pennanen <jari.pennanen@gmail.com> wrote:

Show 10 quoted lines

> 2013/3/4 Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>:
>> There is already core.excludesfile, which does not replace the usual
>> .gitignore but comes in addition. The common use is a user-wide ignore
>> file, not a per-directory one.
>
> I'm actually aware of that. Problem is the normal .gitignore files
> must *not* be used in the second GIT_DIR at all, in my case it's for
> syncing so I need to sync almost all files (including stuff inside
> .gitignore), though I'd still like to retain some ignore files for
> second GIT_DIR, e.g. like in rsync the .rsync-filter file.

How about .git/info/exclude in the 2nd GIT_DIR?  Would that help?

-- 
David

Jari Pennanen· Mar 5, 2013, 10:28 UTC · re: David Aguilar · lore

Re: Configurable .gitignore filename?

2013/3/5 David Aguilar <davvid@gmail.com>:

Show 8 quoted lines

> On Mon, Mar 4, 2013 at 7:47 AM, Jari Pennanen <jari.pennanen@gmail.com> wrote:
>> I'm actually aware of that. Problem is the normal .gitignore files
>> must *not* be used in the second GIT_DIR at all, in my case it's for
>> syncing so I need to sync almost all files (including stuff inside
>> .gitignore), though I'd still like to retain some ignore files for
>> second GIT_DIR, e.g. like in rsync the .rsync-filter file.
>
> How about .git/info/exclude in the 2nd GIT_DIR?  Would that help?

The second GIT_DIR must not use the .gitignore files of the first GIT_DIR, so it does not help.

Only way to skip the .gitignore files in git-add is to use "git add -f ." but that skips all excludes, including the .git/info/exclude. I need to skip .gitignore files used by the other GIT_DIR and still have some of ignore rules, IMO this is not possible at the moment.