| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Abhijit Menon-Sen <ams(at)toroid(dot)org> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Easy way to verify gitignore files? |
| Date: | 2010-09-23 02:19:45 |
| Message-ID: | 4401.1285208385@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Abhijit Menon-Sen <ams(at)toroid(dot)org> writes:
> At 2010-09-22 20:54:19 -0400, tgl(at)sss(dot)pgh(dot)pa(dot)us wrote:
>> However, it seems that git isn't so willing to tell you about gitignore
>> patterns that cover too much, i.e. match files that are already in the
>> repository.
> If .gitignore specifies a pattern that matches something that's already
> in the repository, that specification is itself ignored, and the file is
> treated like any other file.
I can demonstrate that this is not so. Try a "git add" on such a file.
It fails --- at least it does with the version of git currently in
Fedora 13. You get some nasty warning about how there's a conflicting
.gitignore pattern and you have to use -f if you want to add.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abhijit Menon-Sen | 2010-09-23 02:34:07 | Re: Easy way to verify gitignore files? |
| Previous Message | Brendan Jurd | 2010-09-23 01:31:01 | Re: Easy way to verify gitignore files? |