| From: | Brendan Jurd <direvus(at)gmail(dot)com> |
|---|---|
| To: | Abhijit Menon-Sen <ams(at)toroid(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Easy way to verify gitignore files? |
| Date: | 2010-09-23 01:31:01 |
| Message-ID: | AANLkTikR6cSEVpUBq5adc+BHsC_MYU-Ty+2KGp3-spyx@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 23 September 2010 11:28, Abhijit Menon-Sen <ams(at)toroid(dot)org> wrote:
>> 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.)
>
Right; .gitignore patterns are only applied to untracked files. Once
a file is tracked by git, you can try to gitignore it all you like, it
won't have any effect.
Cheers,
BJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-09-23 02:19:45 | Re: Easy way to verify gitignore files? |
| Previous Message | Abhijit Menon-Sen | 2010-09-23 01:28:33 | Re: Easy way to verify gitignore files? |