On Wed, 2009-04-15 at 02:56 -0400, Bill Bogstad wrote: > The downside is that if an individual developer has a personal > workflow which generates other temp files, if they add those files to > .gitignore > those idiosyncratic changes will eventually be pushed back to the > 'master' repository. (Assuming they commit them in their local > repository so as to get a clean 'git status' output.) One possibility > would appear to be to use the .git/info/exclude file for project wide > exclusions while using .gitignore for developer/private exclusions. I > came to this conclusion after reading 'git help gitignore'.
I think you have that reversed. .git/info/exclude is specific to a given repository and is not copied on clone/push/etc. So you want to put "project standard" excludes in .gitignore and "personal" excludes in .git/info/exclude . -- Jeremy _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
