Invoking context menu ".cvsignore" on a ".cvsignore" file correctly inserts the text ".cvsignore" to the file ".cvsignore" and then asks if file ".cvsignore" should be added to CVS :)
Invoking context menu ".cvsignore" on a ".cvsignore" file correctly inserts the text ".cvsignore" to the file ".cvsignore" and then asks if file ".cvsignore" should be added to CVS :)
Ask a computer to do a stupid thing, and most of the time it will do it ;)
Ciao, Gordon
-- Gordon Tyler (Software Developer) Quest Software <http://www.quest.com/> 260 King Street East, Toronto, Ontario M5A 4L5, Canada Voice: (416) 933-5046 | Fax: (416) 933-5001
Pardon me for being a CVS moran, but shouldn't it be in CVS?
The folder which I wanted to ignore contains obfuscation logs for our application. I never want to check those in, even I built an obfuscated version for testing locally. Still if I check in the ".cvsignore", then our build server who builds 'official releases' won't check in the obfuscation logs, either. But for those 'official builds' we need the obfuscation logs.
Pardon me for being a CVS moran, but shouldn't it be in CVS?
Stephen Kelvin wrote:
Ask a computer to do a stupid thing, and most of the time it will do it ;)
Ciao,
Gordon
--
Gordon Tyler (Software Developer)
Quest Software <http://www.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: (416) 933-5046 | Fax: (416) 933-5001
Patrik Andersson schrieb:
The folder which I wanted to ignore contains obfuscation logs for our application.
I never want to check those in, even I built an obfuscated version for testing locally.
Still if I check in the ".cvsignore", then our build server who builds 'official releases'
won't check in the obfuscation logs, either.
But for those 'official builds' we need the obfuscation logs.