david@xxxxxxx writes: > I've got a directory tree that holds config data for all my > servers. This consists of one directory per server (which is updated > periodically from what is currently configured on that server), plus > higher level summary reports and similar information. > > today I have just a single git tree covering everything, and I make a > commit each time one of the per-server directories is updated, and > again when the top-level stuff is created. It is quite clear to me what you are keeping at the top-level files, but if a large portion of the configuration for these servers are shared, it might not be a bad idea to have a canonical "gold-master" configuration branch, to which the shared updates are applied, with a branch per server that forks from that canonical branch to keep the machine specific tweaks as differences from the canonical stuff, instead of having N subdirectories (one per machine). -- 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