From: | Abhijit Menon-Sen <ams(at)toroid(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Easy way to verify gitignore files? |
Date: | 2010-09-23 01:28:33 |
Message-ID: | 20100923012833.GA12781@toroid.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
> This seems pretty dangerous, especially for people who are willing to
> rely on "git commit -a" :-(
There is no danger. "git commit -a" will commit changes to files that
match .gitignore but are already in the repository. (I vaguely remember
that there were bugs in this regard in old versions of git, but it's not
a problem with any recent version AFAIK.)
-- ams
From | Date | Subject | |
---|---|---|---|
Next Message | Brendan Jurd | 2010-09-23 01:31:01 | Re: Easy way to verify gitignore files? |
Previous Message | Tom Lane | 2010-09-23 01:14:10 | Re: Easy way to verify gitignore files? |