git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to manage parameter files and code separately using git?

From
Junio C Hamano <gitster@pobox.com>
Date
May 2, 2010, 15:52 UTC
Message-ID
<7vmxwiuwr5.fsf@alter.siamese.dyndns.org>
In-Reply-To
<op.vb2ms4r8a8ed4e@dellschleppa>
"Tilo Schwarz" <tilo@tilo-schwarz.de> 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.

Previous: Tilo Schwarz
Message 4 of 4 in “How to manage parameter files and code separately using git?”
  1. Tilo SchwarzMay 1, 2010
  2. Junio C HamanoMay 1, 2010
  3. Tilo SchwarzMay 2, 2010
  4. Junio C HamanoMay 2, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.