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

How to propagate critical fixs from master to develope branch.

From
MBMgr Georg Black <georg.black@seznam.cz>
Date
Nov 22, 2018, 06:39 UTC
Message-ID
<FTG.5ClN.5saZnXxVpgT.1Rzay9@seznam.cz>

Hello everyone.I red git manual but I can't figure out how to propagate critical change from master branch to long live develop branch. I red chapter about rebasing that I think could solve it but at the end of this chapter is written that it's not recommended for pubic repositories. I don't know how to do it without merging develop branch to master. I'll appreciate list of orders very much. :-) Thanks for any info or link. GB

Next: Mateusz Loskot
Message 1 of 3 in “How to propagate critical fixs from master to develope branch.”
  1. Mgr Georg BlackNov 22, 2018
  2. Mateusz LoskotNov 22, 2018
  3. Andrew ArdillNov 23, 2018

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.