"Tilo Schwarz" <tilo@xxxxxxxxxxxxxxx> writes: > I see. So if I want parameter file history the only proper solution is to > have a separate parameter file git repo, right? I wouldn't say it is "the" "only" proper solution, but under your design constraint that dictates that the part that is left in "config" (which includes the tracked-and-tied-to-the-software-version "config.sample") must have a history that is independent from the software history, it is one workable solution that would be the easiest. I can imagine a more elaborate implementation that stores the history of that config file on a separate branch in the same repository and manipulate that file with custom scripts, and that also would be another workable solution. -- 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