On Fri, Nov 14, 2008 at 11:16 AM, Ivan Senji <ivan.senji@xxxxxxxxx> wrote: > On each location that i develop some project and configuration files are > different. But i would like them to be in the repository as a starting point > when checking out a project (example: opening a project on a dfferent OS in > eclipse... eclipse will find an error in the path to jdk and ask me to fix > that error by selecting a different jdk). > > How to achieve that these files are in the repository but that any further > changes to them are not commited (or are commited localy but not pushed to a > remote repository)? Hi, Well, if it were me, I think I would commit that eclipse config file under a different name... Say, ".classpath.defaults" instead of ".classpath". Then your README file could tell your users to start by copying the .classpath.defaults to .classpath, and update its contents as necessary. Put .classpath in your .gitignore file, so it won't be committed to the repository. -Tor Arvid- -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
