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

Re: [PATCHv3] Add branch management for releases to gitworkflows

From
RGRaman Gupta <rocketraman@fastmail.fm>
Date
Nov 12, 2009, 20:30 UTC
Message-ID
<4AFC7069.1020701@fastmail.fm>
In-Reply-To
<2729632a0911121208r1f51cf9ewb0bc23e757275f30@mail.gmail.com>
skillzero@gmail.com wrote:
Show 9 quoted lines
>> +.Update maint to new release
>> +[caption="Recipe: "]
>> +=====================================
>> +* `git branch -f next master`
>> +* `git merge ai/topic_in_next1`
>> +* `git merge ai/topic_in_next2`
> 
> Shouldn't that be something like "Update next to new release" instead
> of "maint"?
Oops. I changed the caption to "Rewind and rebuild next".
> Should it also have 'git checkout next' after the branch command so
> it's on next before merging?
Right, fixed also.

Thanks, Raman

Previous: skillzero@gmail.comNext: Nanako Shiraishi
Message 4 of 16 in “Add branch management for releases to gitworkflows”
  1. rocketraman@fastmail.fmNov 12, 2009
  2. [PATCHv3] Add branch management for releases to gitworkflowsrocketraman@fastmail.fm, Nov 12, 2009
  3. skillzero@gmail.comNov 12, 2009
  4. Raman GuptaNov 12, 2009
  5. Nanako ShiraishiNov 13, 2009
  6. Raman GuptaNov 13, 2009
  7. Nanako ShiraishiNov 13, 2009
  8. Raman GuptaNov 14, 2009
  9. Björn GustavssonNov 14, 2009
  10. Nanako ShiraishiNov 14, 2009
  11. Raman GuptaNov 14, 2009
  12. Junio C HamanoNov 15, 2009
  13. Thomas RastNov 15, 2009
  14. Raman GuptaNov 18, 2009
  15. Thomas RastNov 18, 2009
  16. Nanako ShiraishiNov 19, 2009

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.