Re: Add .gitignore files to CVS?
От | Robert Haas |
---|---|
Тема | Re: Add .gitignore files to CVS? |
Дата | |
Msg-id | 603c8f071001080934x6d09a004p8eee1e27fb7982ad@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Add .gitignore files to CVS? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Add .gitignore files to CVS?
|
Список | pgsql-hackers |
On Thu, Jan 7, 2010 at 5:45 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Peter Eisentraut <peter_e@gmx.net> writes: >> On tor, 2010-01-07 at 22:16 +0000, Tim Bunce wrote: >>> Is there any reason not to add .gitignore files into the repository? > >> I already find the .cvsignore files to be useless and an annoyance to >> keep up to date (well, I basically ignore them and someone else cleans >> up after me), > > When/if we move off CVS, we should drop the .cvsignore files and insert > .gitignore (assuming that works the same way). I am not in favor of > expecting the core project to maintain support for non-core SCMs though. > Will we have .bzrignore and who knows what else in there too? > > As Peter points out, the only way the things will get maintained is if > the complaints they suppress are in-the-face of somebody with commit > access to the core repo. I like quiet from my "cvs update"s, so I'm > willing to maintain .cvsignores, but I'm not willing to maintain > multiple copies of that information. I would be willing to maintain .gitignore files, under the agreement that if I should fail or cease to do so, and no one else wants to take over, then they all get removed. Would that be acceptable? ...Robert
В списке pgsql-hackers по дате отправления: