2013/3/5 David Aguilar :
> On Mon, Mar 4, 2013 at 7:47 AM, Jari Pennanen 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
>> .gi
On Mon, Mar 4, 2013 at 7:47 AM, Jari Pennanen wrote:
> 2013/3/4 Matthieu Moy :
>> 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
2013/3/4 Matthieu Moy :
> 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 seco
Jari Pennanen 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 = .gitalternateignore
There is alrea
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 filen
5 matches
Mail list logo