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

Re: Big Mess--How to use Git to resolve

From
Hhs_glw <greg@hra.net>
Date
Dec 17, 2011, 18:40 UTC
Message-ID
<1324147247781-7104493.post@n2.nabble.com>
In-Reply-To
<86iplf2oy5.fsf@red.stonehenge.com>

Randal, thank you for the comprehensive answer. I have one follow-up: we have the working files, then in our installation files we have .PL files that are worked on by some iteration of "make" to insert paths both into .cgi files and config files, should these installation files be setup as a branch? or is there a more correct way of implementing this?

-- View this message in context: http://git.661346.n2.nabble.com/Big-Mess-How-to-use-Git-to-resolve-tp7103964p7104493.html Sent from the git mailing list archive at Nabble.com.

Previous: Randal L. SchwartzNext: Holger Hellmuth
Message 3 of 7 in “Big Mess--How to use Git to resolve”
  1. hs_glwDec 17, 2011
  2. Randal L. SchwartzDec 17, 2011
  3. hs_glwDec 17, 2011
  4. Holger HellmuthDec 19, 2011
  5. Neal KreitzingerDec 21, 2011
  6. Neal KreitzingerDec 21, 2011
  7. Seth RobertsonDec 21, 2011

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.