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

Centralized processes in git

From
RBRobert Boone <robert@rlb3.com>
Date
Aug 20, 2007, 18:30 UTC
Message-ID
<31FEEAE6-58A6-4A74-9DB7-E6F9D56D1C48@rlb3.com>
Hello,
     My company is looking at git to replace subversion as our scm.  
We have a small team of developers which need to publish to a  
centralized repository. One thing we would like is to have an  
automated bug fix merge ability. So if I make a bug fix to master we  
want that fix to be merged into other branches that we set. If there  
is a conflict we want that person  to be notified by email or some  
other way. I would like to know if anyone on the list has a good way  
to implement this?
Next: Jan Hudec
Message 1 of 5 in “Centralized processes in git”
  1. Robert BooneAug 20, 2007
  2. Jan HudecAug 20, 2007
  3. Steven GrimmAug 21, 2007
  4. Steven GrimmAug 21, 2007
  5. Jeff KingAug 21, 2007

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.