Olivier Galibert <galibert@xxxxxxxxx> writes: > I've got a number of a little over one year old repositories I do my > private stuff into. Looks like in that year things changed quite a > bit (remote going from files to some kind of config file? reflog > stuff?). What should I do to change them to what would be considered > an up-to-date, full bells-and-whistles configuration? A better question to ask before that is "do I need to change to take advantage of any bells-and-whistles", I think. * To enable reflog in your repository with working-tree, you do not have to do anything. It's on by default. * $GIT_DIR/remotes/origin is still consulted for a pull/fetch. If you do not do complicated multi-branch workflow, you do not gain much by moving that information to .git/config. There is a contrib/remotes2config.sh script that copies information from remotes/origin into .git/config if you are interested. - 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