On 04/07/12 21:28, Justin Deoliveira wrote: > Well the idea is that .gitignore is just any other versioned filed. Why > not just change it accordingly and commit it. On updating handling any > conflicts like anything else.
In my view, only core developers should be messing with top-level files that affect the whole community; we encourage new developers and new maintainers to stick to their modules. I think what you have done is a good pattern: decent shared defaults in the top-level .gitignore. Then individuals can add their own ignores in .git/info/exclude and Macincruft like ._* in their global ignores. > Indeed. But given my todo list a few stray files lying around is pretty > low priority. Sure. I just put them in my .gitignore (now .git/info/exclude) and forgot them. I think we are in agreement. :-) Kind regards, -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
