On Mon, Mar 4, 2013 at 7:47 AM, Jari Pennanen jari.penna...@gmail.com wrote:
2013/3/4 Matthieu Moy matthieu@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
2013/3/5 David Aguilar dav...@gmail.com:
On Mon, Mar 4, 2013 at 7:47 AM, Jari Pennanen jari.penna...@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
Jari Pennanen jari.penna...@gmail.com writes:
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 =
2013/3/4 Matthieu Moy matthieu@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
4 matches
Mail list logo